Using the Journal Builder to Enter Site-Specific Journal Transactions

Use the Journal Builder form to enter site-specific pending journal transactions, which are then validated and created in the Multi-Site journal at the specified site.

1. Set up Replication Rules for the Journal Builder category:
   • From the Journal Builder site to all remote sites into which pending Multi-Site journal transactions will be inserted.
   • From those remote sites back to the Journal Builder site.
2. Log into the site where pending Multi-Site journal transactions will be entered and open the Journal Builder form.
3. Enter a transaction date that is valid for the local site.
4. Enter site-specific journal transactions.
5. When all the transactions are entered and the amounts in the Debit and Credit total fields in the header are balanced, click Process.

If validation is successful, a success message displays, which contains the control number generated by the Journal Builder utility. The pending journal transactions are then inserted in the Multi-Site Journal in the specified site(s) and a success message displays . The transactions have a batch control number that includes the site ID of the Journal Builder site, for audit purposes.

If validation is not successful:

• If the To Site is the local site, or if replication is transactional from the local site to the remote site, the system returns an error and no transactions are processed.
• If the To Site is not the local site AND if replication is non-transactional, failures must be handled at the remote site. The local site will be unaware that an error occurred. For more information, see the note below about non-transactional replication.

Notes

• Journal Builder use at an entity, or to enter transactions to be inserted at an entity, is not supported.
• Transactions can be entered only for sites that use the same domestic currency as the local Journal Builder site.
• When you close the Journal Builder form, any unprocessed rows are removed.
• The control number is based on the site where the pending journal entries are entered through the Journal Builder, so all the transactions in one batch have the same control number.
• Non-transactional replication: If processing is non-transactional and fails for some reason at a remote site, the entire transaction will not be backed out. Successful journal entries will be inserted and reside in the Multi-Site journal. Unsuccessful journal entries wil be handled in the same way as any other "failed" process for non-transactional setups. This could result in a Multi-Site journal with transactions where the Total Debits do not equal the Total Credits until the error is resolved.

Related Topics

General Ledger Overview

General Ledger Steps