Edit Statement Dialog
Open Edit from the statement detail page to update metadata and add instructions for the AI. The dialog has three sections.Accounting Period
Set or correct the period covered by the statement:| Field | Description |
|---|---|
| Year | Accounting year (e.g. 2024) |
| Type | Monthly (M), Quarterly (Q), Half-yearly (H), or Annual (Y) |
| Number | For M: 1–12 (January–December). For Q: 1–4. For H: 1–2. Not used for Annual. |
Currency
| Field | Description |
|---|---|
| Transaction Currency | Currency of the underlying sales transactions |
| Royalty Currency | Currency you are paid in |
Instructions
The Custom instructions field is a free-text area that is passed to the extraction/automap process when you run Retry. Use it to guide the LLM when the statement has an unusual layout or naming. Examples:- “The first column in the PDF is always the track title, not the ISRC.”
- “Ignore the first two header rows on every page.”
- “Map the column labeled ‘Net Amount’ to Licensor Revenue.”
- “This statement has two revenue tables; the second one starts on page 4.”
Best Practices for Instructions
Use for unusual layouts
Use for unusual layouts
PDFs and spreadsheets with non-standard structure (e.g. merged cells, multiple tables, inconsistent headers) benefit from short, concrete instructions.
Be specific
Be specific
Refer to exact column names, row positions, or page numbers when possible (e.g. “Column D is royalty amount” rather than “one of the columns has the amount”).
One concern per instruction
One concern per instruction
Split complex guidance into separate sentences so the model can apply each rule clearly.
Retry after editing
Retry after editing
After saving Edit (period, currency, or instructions), use Retry so the statement is reprocessed with the new settings. Instructions are only used during processing.
Retry Processing
Retry (in the statement header actions) reruns the automap/extraction process for this statement. Use it when:- You have updated accounting period, currency, or instructions in Edit and want to re-extract with the new metadata
- A previous run failed or produced low confidence and you want to try again
- You fixed the source file and re-uploaded (or you want to re-run without re-uploading)
View Mappings
View Mappings opens a view of how columns in the uploaded file were mapped to statement fields (e.g. which column became “Licensor Revenue”, “Track Title”, etc.). Use it to:- Understand why a value ended up in a given field
- Debug extraction when totals or line items look wrong
- Decide what to put in Instructions for the next Retry
Related Documentation
Statement Details
Tabs and all header actions.
Upload
Processing pipeline and statuses.