The Voucher package allows for the creation of transactions:
- Journal Entries
- Accounts Payable
- Accounts Receivable
- Cash Transactions
A distinct user id should be created to use with these APIs. This user could have their password change frequency set to never, if required. If never is not chosen, the third party will need to be updated on password changes with enough notice to make any required changes.
If the volume of transactions is expected to be high this user id should be assigned the Qbyte Connect queue. This will separate the loading of third party transactions from day-to-day processing, like voucher posting and payment processes.
A distinct Voucher Type should be created to use with these APIs. The Voucher Type must have Auto Numbering turned on.
Initial invoice creation as well as invoice adjustments are supported.
DOIs will be assigned using the standard data entry rules.
Care must be taken to ensure invoice links are created and maintained.
A pre-validation API is available and should be used to perform any possible validation prior to loading the data.
Applicable system defaults will be applied when specific data is not provided. Details of these can be found in the API documentation.
Create User, Create Date, Last Update User, and Last Update Date will be populated with the user id included with the third party call. Audit records are created for all updates.
The data is first loaded into temporary tables to ensure that all data integrity rules are followed.
The following APIs are included in the Transactions package:
- Validation API – Used for pre-validation.
- External Transactions API – Used to load and validate entries.
- Assign DOI API – Assigns appropriate DOI.
- Transaction Status API – Used to return status to third parties.