Jurnal data objects and sync direction
Start with a list of the objects you need: suppliers or customers, ledger accounts, invoices, payments and journal entries. You and the implementation team map this list together. Support for each object has to be confirmed for your Jurnal account before activation.
- The flow described on this page: documents come into Finday.ai, the drafts are reviewed, and approved data goes to Jurnal by the method you agree on.
- If reference data has to be read from Jurnal, decide which system is the main source, how each transaction is identified and how updates are handled, so nothing is recorded twice.
- Two-way sync, real-time schedules and coverage of every object are not included by default. Write the direction, frequency and objects into the implementation scope.


