How to use a Righthand with Dext
Prepare a reviewed document-to-line-item review register from approved Dext inputs, with a worked example, complete brief, access checks, and reconciliation.
Quick answer
Use an approved Dext extract to prepare a review register that distinguishes source documents from their line items. This gives the bookkeeper a clear map of missing fields and inconsistent totals before accounting review.
Start with a document-to-line-item review register that the bookkeeping reviewer can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.
Establish the input route
Dext’s custom CSV guide distinguishes one-row-per-item exports from line-item exports and describes configurable decimal, date, and column preferences. Official Dext reference, checked October 6, 2026.
Ask the account administrator which export format was used and include that format name with the supplied file. Preserve the original document reference and clarify whether each row is an item header or a detail line.
Check the current integration directory and Righthand setup documentation. A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.
Worked input and output
These three records are synthetic illustrations, not customer results or a hands-on integration test.
| Approved input | Proposed review output |
|---|---|
| D31: one header and two detail rows | Group both lines beneath D31; count one source document |
| D32: date 10/12/2026; date convention unspecified | Flag date interpretation before assigning the reporting period |
| D33: amount uses comma decimal separator | Retain original numeric string; request confirmed decimal convention |
The register should not sum a document header together with its detail lines. D31’s grouping is the first acceptance check. D32 illustrates why a familiar-looking date is insufficient: the export settings, rather than the reader’s locale, determine its meaning.
A complete first-run brief
Use an approved Dext CSV extract and source-document index for October 12–16, 2026. Fields: document ID, document date, supplier, row type, line reference, net amount, tax amount, gross amount, currency. At Monday 9 AM America/Los_Angeles, prepare a document-to-line-item review register as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: bookkeeping reviewer. Do not publish to accounting software, classify tax treatment, approve documents, or change export settings. Result check: Check one grouped document against its source image and verify that header totals are not counted twice.
A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.
Reconcile before widening the task
A custom column selection may omit a needed field even when the export succeeds. Mark absent currency or document identity as a source gap. Supplier names alone are weak grouping keys, especially when several documents from one supplier share a date.
Trial the register with one bookkeeper and a small approved document slice. Record the accepted export conventions beside the review criteria. On the next run, detect a changed column set before comparing results across periods.
For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review Pricing using the actual preparation workload and correction effort.