This article explains
How to push transaction and receipt data from Pliant to Oracle Netsuite
How data is stored in Oracle Netsuite
Important: To complete the steps described below you first need to make sure Pliant is connected to Oracle Netsuite successfully by following this article and you have imported/synced data fields from Oracle Netsuite by following this article.
Pre-accounting within Pliant
Use Pliants Accounting export flow to assign pre-accounting values either
manually (web & mobile app)
automatically via
card- & merchant based automations
receipt inbox
For details on this topic please see this set of articles.
In short, the accounting export flow is the place to keep track of all the credit card transactions and receipts before exporting it to Oracle Netsuite. There are three subpages available:
Not exported: All non exported card transactions that (most probably) still need some information (G/L accounts, vat rates, receipts...)
Export queue: Credit card transactions and receipts that are ready to be pushed to Oracle Netsuite.
Exported: Credit card transactions and receipts that have been pushed to Oracle Netsuite and cannot be modified anymore.
The status of the export as well as any potential issues are directly shown within Pliant export flow.
If you export multiple transactions and some of them cannot be exported only the individual transaction are going to be rolled back to Export Queue, hence we do support partial exports.
How does the data appear in Oracle Netsuite
(1) Where do I find the Pliant Transactions?
Depending on Bank Account type setup in General accounts
For type CREDIT navigate to Transactions > Bank > Use Credit Cards > List
For type PREPAID navigate to Transactions > Bank > Write Cheques
(2) How is data stored in Netsuite and what booking lines are created?
Transaction Data
Receipt data
Booking Entries
Important: Transactions can be edited afterwards
