After an invoice has been fully approved and validated, Onit typically hands it over to an Accounts Payable Team and/or system to pay. There are multiple ways to facilitate this exchange:

• Flat-file Integration: This is the most common and recommended integration style. Using an SFTP server, Onit exchanges flat files with a client. Onit generates an “invoices to pay” flat-file, which the client consumes; the client generates an “invoices paid” flat-file, which Onit consumes. Flat files are usually generated and consumed using ETL jobs or other middleware tools.
   
• API-based Integration: Though less common, exchanging invoice data via APIs is possible. Onit can initiate calls to an Accounts Payable system’s API, and/or the AP system can make calls against Onit’s RESTful API.
   
• Email-based Integration: In a small number of cases, clients prefer that Onit only send emails to an Accounts Payable Team listing the invoices that need to be paid. This is often done in place of a more robust flat file or API integration.

After the Invoices Record is fully approved and validated, a new Record will be created in a separate child App named Invoice Payment. All integration jobs facilitating sending payments to an Accounts Payable Team or system will exclusively interface with Records in the Invoice Payment App; integration jobs should never interface directly with Records in the Invoices App.

Throughout the payment process, the Invoices App and Invoice Payment App’s Phases stay in lock-step concerning Phases (this is done using a configuration already existing in the environment). Any Phases that follow your custom approval process (i.e., Phases Approved through Paid) should not be edited or deleted; none of the Phases in the Invoice Payment App should be edited or deleted.