Document guide
Payment demand
Identify who requests payment, from whom, for what amount and under which references. Classify court payment orders and payment communications while retaining each document’s source and context.
Explore fields and examples ↓The information your team needs.
Amounts claimed, references and document dates. Each value retains its document reference so the team can return to the source during review.
Illustrative fields · Fictional data. Fields and output are configured for the supplied documents and agreed workflow.
| Field | What it contains | Example |
|---|---|---|
| Sender | Court, entity or party requesting payment. | Entity A |
| Recipient | Recipient identity and role. | Debtor B |
| Reference | Agreement, file or proceedings. | OP-0042 |
| Amount requested | Explicitly stated amount and breakdown. | €3,200.00 |
| Date and receipt | Available issue date and receipt evidence. | Issued: 30 Sep 2026 |
| Period and action | Instructions and period as written. | Payment requested · period stated in text |
Connect the data. Find what needs attention.
Associate the amount with its claimed components and date, rather than equating it with original principal.
Check references and retain the request separately from its receipt.
Service, legal effects and deadline calculation are assessed using the case documents.
Information ready for your workflow.
A case entry with the amount, recipient and stated action. Receive an Excel or CSV file for review, or structured data in the format agreed for your system.
Use it in these solutions
Try it with a batch of your documents. We agree the sample, fields and confidentiality before starting.
Discuss my batch →