There is a close relationship between these three header-level date fields:
Invoice Date
Payment Terms
Invoice Due Date
Ideally, each invoice will have these three attributes, but some will have only two, or perhaps just an invoice date.
Vendor Payment Terms
If Payment Terms are sourced from the vendor record, you will instead see a small ✅ . The AI will not make any predictions, and instead default to the stored vendor payment terms.
Invoice Dates and Payment Terms Mismatch
Vic.ai will flag for you, via a yellow box outline, if there is a mismatch between the invoice date, payment terms, and invoice due date.
If you enter the due date field, you will see an option to calculate:
"Compute invoice date + payment terms = Due Date." Selecting it will perform the math of Invoice Date + Payment Terms" to bring the Due Date into alignment.
GL (General Ledger) Date
This field is used to control the accounting period that an invoice posts to. This can also vary by integration or middleware behavior.
GL Date Configuration Options:
Normal Behavior: GL Date is the predicted invoice date. This can be modified before posting.
Posted Date: GL Date is set to today's date in the company's billing timezone when an invoice is posted/exported to the ERP. GL Date should likely not be added to the UI as the original value will be overwritten by this behavior.
Questions about your setup, or looking to switch to a different option? Contact your Customer Success Manager or Customer Support