The Accounts Payable and Receivable AI engine is pre-trained to recognize Rossum’s general dataset of semi-structured documents. Rossum generic AI engine has been specifically trained to recognize invoices and purchase orders.
Rossum’s Accounts Payable and Receivable AI Engine has been pre-trained to recognize data fields in invoices and purchase orders. You can use this engine to automate your AP and AR processes without any complex training procedures. The engine supports most standard invoicing fields.
The tables below contain the full list of standard data fields the Accounts Payable and Receivable AI Engine can extract.
Note: If you want to reach better extraction results on non-standard data fields, you’ll need to use Rossum’s Dedicated AI Engine.
|Type of the document
|Currency of the document
|Language of the document
|Bank account number
|Bank code that identifies bank and branch location
|Bank account number in IBAN format
|Bank BIC or SWIFT code
|Statistical code on payment order
|Number assigned to a customer registered in a supplier’s accounting system
|Invoice payment due date
|Document date of issue
|Tax Point Date
|The date of taxable event
|Purchase order identification number
|Address of the customer
|Recipient Tax Number
|Tax identification number of the customer
|Recipient Company ID
|Company identification number of the customer
|Name of the customer
|Recipient VAT Number
|Customer VAT Number
|Recipient Delivery Name
|Name of the recipient to whom the goods will be delivered
|Recipient Delivery Address
|Address of the recipient where the goods will be delivered
|Address of the supplier
|Supplier Tax Number
|Tax identification number of the supplier
|Supplier Company ID
|Business/organization identification number of the supplier
|Name of the supplier
|Supplier VAT Number
|VAT identification number of the supplier
|Email of the supplier
|Supplier’s Order ID
|Internal order ID in the suppliers system
|Payee ID on the payment order or similar
|Payment terms as written on the document (e.g. 45 days upon receipt)
|In some countries, used by the supplier to match the payment received against the invoice
|Payment method defined on a document (e.g. Cheque, Pay order, Before delivery)
|Delivery Note ID
|Delivery note ID defined on the invoice
|Place of Supply
|Place of supply (the name of the city or state where the goods will be supplied)
|Final amount, including tax to be paid after deducting all discounts and advances
|Remainder after rounding up total amount
|Subtotal of all items, including tax
|Amount that has already been paid
|Tax Base Total
|Base amount for tax calculation
|Total tax amount
Tax details table
|Sum of tax bases for items with the same tax rate
|One of the tax rates in the tax breakdown
|Sum of taxes for items with the same tax rate
|Total amount, including tax for all items with the same tax rate
|Text on document describing tax code of the tax rate (e.g. GST, CGST, DPH, TVA). If multiple tax rates belong to one tax code on the document, the tax code will be assigned only to the first tax rate
Line items table
|Can be the SKU, EAN, a custom code (string of letters/numbers), or even just the line number
|Line item description. Can be multi-line with details.
|Quantity of the item
|Item Unit of Measure
|Unit of measure of the item (kg, container, piece, gallon, …)
|Tax rate for the line item
|Tax amount for the line. Rule of thumb: tax = rate * amount_base.
|Unit price without tax (this is the primary unit price extracted)
|Unit price with tax. Rule of thumb: amount = amount_base + tax.
|Amount Total Base
|The total amount to be paid for all the items, excluding tax. Rule of thumb: amount_total_base = amount_base * quantity.
|The total amount to be paid for all the items, including tax. Rule of thumb: amount_total = amount * quantity.
|Unrecognized data type
To find our more information on mapping your own fields in the extraction schema, visit our API documentation.