Maintained by:

Connected Systems

Zuora Revenue (source)
Platypus (middleware)
Workato (middleware)
Netsuite (destination)

Summary

This integration is responsible for taking Zuora Revenue Journal Entries and creating Netsuite Journal Entries. This occurs monthly at the end of the month. The integration groups and summarises journal lines into Journal Entries whereby each Entity has n JEs depending on the grouping of the fields GL Account Number and Product Rate Plan Charge. Each resulting entry is summarised by summing the credit lines and separately summing the debit lines.

There are issues with rounding differences and decimal place expectations between systems so we had to solve that via the solution outlined in this issue.

Sequence

sequenceDiagram participant Accounting Team participant Platypus participant Platypus Queue participant Workato participant Zuora Revenue participant Netsuite loop every end of month % First we receive a trigger from the accounting team Accounting Team ->> Platypus: Trigger Processing activate Platypus Platypus ->> Workato: Fetch Journal Batches Workato ->> Zuora Revenue: Fetch Journal Batches Zuora Revenue -->> Workato: Batch List loop for every batch Platypus ->> Platypus Queue: Create job for batch end deactivate Platypus % We process batch by batch Platypus Queue ->> Platypus: On new job activate Platypus Platypus ->> Workato: Fetch batch lines Workato ->> Zuora Revenue: Fetch batch lines Zuora Revenue -->> Workato: Batch lines Workato -->> Platypus: Batch lines Note left of Platypus: Platypus validates, resolves and Journal data loop for each batch line Platypus ->> Workato: Resolve Class, Account and Product Rate Plan Charge Workato ->> Netsuite: Resolve Class, Account and Product Rate Plan Charge Netsuite -->> Workato: Results Workato -->> Platypus: Results end Platypus ->> Platypus Queue: Job to Create JE deactivate Platypus Platypus Queue ->> Platypus: On new JE Job activate Platypus Platypus ->> Workato: Create Journal Entry Workato ->> Netsuite: Create Journal Entry Netsuite -->> Workato: Netsuite JE ID Workato -->> Platypus: Netsuite JE ID deactivate Platypus Note over Platypus,Netsuite: Once all the Journal entries for a batch are created in Netsuite Platypus ->> Zuora Revenue: Mark batch as transferred end

Error handling

When validation errors occur on the incoming data from Zuora revenue we will post to #alerts_revenue-accounting-integration slack channel which is monitored by the Accounting Team.

When errors occur with issues downstream in Netsuite we will post to the #finsys-integrations slack channel which is monitored by the Finance Systems Administration team.

Data Model

Each journal entry has many lines

erDiagram JOURNAL_ENTRY ||--|{ JOURNAL_LINE: Has

Zuora Revenue Field	Netsuite Field	Canonical Field
id	Source System Reference	Batch ID
reference5	Subsidiary	Entity
currency_code	Currency	Currency Code
memo	Memo	Memo
reference9	postingperiod	Accounting Period Name
segment1	Line > Account	GL Account Number
N/A^*	Line > Department	Department
accounted_dr	Line > Debit Amount	Accounted Debit
accounted_cr	Line > Credit Amount	Accounted Credit
reference8	Line > Class	Classification
N/A^†	Line > Memo	Line Memo

^* Department is calculated from the GL Account Number (relevant code)

^† This is always set to REV_Revpro-GL

Security Components

Platypus authenticates with Workato using OAuth2 Client Credentials
Workato Authenticates with Zuora Revenue using a custom built auth scheme
All connections are over HTTPS

Data classification

This integration handles and stores Orange Data (Accounting data)

Environments

Environment	Zuora Revenue	Platypus	Workato	Netsuite
Production	Production	Production	Production	Production
Staging	TBD	Staging	Development/Testing	Sandbox 2
Development	Sandbox 1	Local Dev & Review Apps	Development	Sandbox 1

Zuora Revenue to Netsuite NOT DEPLOYED