Invoices - Datasource
Field | Type | Length | Unique | Required | Format | Description |
|---|---|---|---|---|---|---|
identifier | varchar | 80 | yes | yes |
| Invoice ID. This should preferably be the invoice number of the invoice as displayed on a printed invoice that is produced for tax purposes. |
invoice_type_code | varchar | 255 | no | no |
| Invoice type e.g. invoice, discount, credit... |
issue_date_time | timestamp |
| no | yes | YYYY-MM-DD hh:mm:ss | date/time the invoice was issued. This should be the date that is produced on a printed invoice for tax purposes. |
total | float | 8 | no | yes |
| Total of amount invoiced including sales tax. Discounts and credits should be negative |
tax_total | float | 8 | no | yes |
| Total amount of tax. Discounts and credits should be negative |
client | varchar | 255 | no | yes | table: clients, field: identifier | Client ID of the client the invoice is issued to. This should be the unique identifier of the client/customer |
status | varchar | 20 | no | no |
| e.g. paid/partly_paid. If partly paid invoices are included in the supplied data then all invoices must be flagged as paid/partly paid. As an alternative it is acceptable to supply only fully paid or finalised invoices |
branch | varchar | 255 | no | yes |
| Name/Code/ID of the branch/location/job/department the invoice was issued if the system supports different locations, branches, jobs or departments. |
updated_after/date_modified | timestamp |
| no | optional if data is to be collected incrementally | YYYY-MM-DD hh:mm:ss | If data is to be collected incrementally, and updates or edits to either invoice header and invoice line needs to be flagged with a timestamp indicating the most recent 'last modified' date |
Example CSV-File: invoices.csv