What to do
Capture the document title, issuer, reference, and stated adjustment before deciding how a debit note should affect another record. Terminology and usage can vary between businesses. The extracted data should preserve what the document says without assigning accounting treatment automatically.
The same adjustment can be described differently from the buyer’s and seller’s perspectives.
Two worked review cases
These cases are fictional teaching data, not measured extraction results. Use the source excerpts to practise deciding what belongs in the reviewed output.
| Case | Fictional source excerpt | Review decision |
|---|---|---|
| Additional charge stated | Seller debit note DN-3; freight correction 8.00 against INV-4 | Retain issuer, reason, and original reference for review. |
| Buyer document | Buyer-issued debit note; goods-return reference RET-7 | Do not infer treatment from the title alone; preserve the stated context. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Document title | Exact printed document type. |
| Debit note number | Identifier assigned to this adjustment document. |
| Adjustment reference and reason | Printed original-document reference and explanation. |
These are suggested staging-sheet columns. Printed facts can inform field descriptions in Parzable’s Schemas view; source references, review statuses, and decisions must be supplied by your own review process.
A practical review sequence
- Identify who issued the note and which party is addressed.
- Capture its own number and any adjusted-document reference separately.
- Ask the accounting reviewer to confirm how this document enters the destination.
Errors to avoid
- Do not assume every debit note represents the same business event.
- A reference to an invoice does not make the note a duplicate of that invoice.
Use the case worksheet with a small sample
Download this page’s worked-case worksheet. It contains the two fictional cases above and a blank row for your own review exercise. Keep any real source documents in your agreed storage process.
For the broader product workflow, see the related guide. Parzable accepts PDF/image inputs and downloads CSV. Suggested structures here are review targets; nested item rows, automatic approvals, and destination integrations are not guaranteed.
Reference and scope
Further reading: Invoice and receipt field roles: Amazon documentation. External documentation provides background for the topic; it does not establish Parzable’s implementation or performance. References checked 18 October 2026.
Examples and review decisions on this page are authored illustrations. Confirm unresolved business, payment, or accounting decisions through the responsible reviewer.
Put the workflow to work
Try your own invoice in Parzable
Create an account, define a schema, and test a small sample. Review extracted values before using them. See current plans and page allowances.
Try Parzable