Statements are the payouts your selling channels send for a period: a Shopify Payments payout, a TikTok Shop settlement or an Amazon settlement report. The bank shows a payout as one amount, and the statement in Pipe17 breaks that amount down into statement transactions: the order payments and refunds it covers, plus fees and adjustments. Pipe17 pulls statements from the channel and can push them to NetSuite as Deposits, so your finance team can match each bank deposit to the orders in your ERP.
Before you start
Turn on statement imports
Statements appear only after a channel integration starts sending them. To turn this on:
- Go to Integrations and open the Shopify, TikTok or Amazon integration.
- Open Settings.
- Turn on the statement setting and set the date cutoff from the table below.
- Click Save, keep the integration enabled and connected, and let its sync run.
| Channel | Setting to turn on | Date cutoff |
|---|---|---|
| Shopify | Pull statements from Shopify (Shopify Payments payouts; off by default) | Exclude statements created before this date |
| TikTok Shop | Pull statements from TikTok | Exclude statements created before this date. If empty, the integration's creation date is used. |
| Amazon Seller Central | Pull settlement reports from Amazon Seller Central (off by default) | Exclude settlement reports created before this date |
Channel-specific options:
- Shopify: for Shopify Plus shops that split Shopify Payments across several business entities, turn on Pull statements from every business entity. Leave it off to pull only the primary entity.
- Amazon: Specify transactions types to pull from settlement reports defaults to Order and Refund. Add other types, such as Chargeback or AdvertisingTransactionDetails, if you need them on the statement.
- Each integration also has an action to pull statements for a date range (for example Pull statements from Shopify by date), which is useful after changing the cutoff.
For channel setup, see Connect Shopify to Pipe17, Connect TikTok to Pipe17 and Connect Amazon Seller Central to Pipe17.
Permissions
| To do this | You need |
|---|---|
| See All Statements and open a statement | Statements: read and list |
| See Transactions, open a transaction, and see the transactions on a statement | Statement Transactions: read and list |
| Push selected statements | Statements: create or update |
| Push every statement that matches a filter | Statements: create or update, and Jobs: create |
If Statements is missing from the menu or Push Statements is unavailable, ask your organization admin for access.
Where to find them
Open Statements in the side menu:
- All Statements lists every payout.
- Transactions lists every statement transaction across all payouts.
Statuses
Statement statuses
| Status | What it means |
|---|---|
| Draft | The channel import has created the statement and is still loading its transactions. |
| Pending | The import has finished and the statement is ready for accounting. With default NetSuite settings, this is the status that pushes the statement. |
| Reported | The accounting integration has written the statement. For NetSuite, the Deposit has been created or updated. |
| New | The statement was created without a status, for example through the API. Channel imports use Draft instead. |
| Deleted | Removed from normal processing. Shown only when you select Deleted in the Status filter. |
A channel import normally moves a statement from Draft to Pending, and the NetSuite push moves it from Pending to Reported.
Reported means the Deposit was written. It does not mean the bank line is reconciled or that the Deposit has no variance, so check Exceptions after a push.
Transaction statuses
| Status | What it means |
|---|---|
| Draft | The line was received and is still being prepared. |
| Pending | The line is loaded and waits to be applied with its statement. Shopify and Amazon imports load transactions as Pending. |
| Reported | The line is marked reported. NetSuite sets this after it processes the line, but TikTok transactions arrive as Reported by default, so this status alone doesn't confirm that NetSuite processed the line. |
| New | The line was created without a status, for example through the API. |
Transactions don't use Deleted.
All Statements
| Column | Shows |
|---|---|
| External Statement ID | The payout's ID in the channel. Click it to open the statement. |
| Status | The statement status. |
| Exceptions | How many exceptions the statement has. Hover to see their categories. |
| Statement Total | The settlement total stored on the statement. |
| Deposit Total | The deposit amount stored on the statement. |
| Deposit Date | When the channel paid out. |
| Statement Start Date / Statement End Date | The period the statement covers. |
| Source Integration | The channel integration that sent it (the source, not the accounting destination). |
| Created | When Pipe17 received the statement. |
| Currency, Statement ID, Updated | Hidden by default. |
The list is sorted by Statement Start Date, newest first. To show, hide or reorder columns, click the grid icon to the right of the refresh button.
Filter statements
There's no free-text search. Use the filters above the list:
| Filter | Use it to |
|---|---|
| Status | Show one or more statuses. Deleted statements appear only when you select Deleted. |
| Created / Updated | Limit by when Pipe17 received or last changed the statement. |
| Statement ID / External Statement ID | Find one statement by its Pipe17 or channel ID. Both match the exact ID. |
| Deposit Date | Limit by when the channel paid out. |
| Statement Start Date / Statement End Date | Limit by the period the statement covers. |
| Integration | Show statements from one channel integration. |
| Exception Categories | Find statements with a type of exception. |
Statement details
Click an External Statement ID to open the statement.
- Information: Statement ID, Integration, Created at and Updated dates, Show related events, and External Statement API ID.
- View Log shows the statement's event history. View JSON shows the full record.
- Statement Summary: Start Date, End Date, Deposit Date, Currency, Statement Total and Deposit Total.
- Transaction Fees: statement-level amounts by name, such as Sales, Refunds and Processing fees. Shown when the channel sends them.
- Transaction Totals: totals rolled up from the statement's transactions. Shown when available.
- Statement Transactions: each transaction with its Transaction ID (a link), Reference ID (usually the order number), Created date and Exceptions.
- On the right: Custom Fields, Statement Activity (related events) and View transactions, which opens the Transactions list filtered to this payout.
Transactions
Go to Statements > Transactions.
| Column | Shows |
|---|---|
| External Transaction ID | The transaction's ID in the channel. Click it to open the transaction. |
| External Statement ID | The payout it belongs to. Click it to open the statement. |
| External Reference ID | Usually the channel's order ID (see below). |
| Status | Draft, New, Pending or Reported. |
| Exceptions | How many exceptions the transaction has. Hover to see their categories. |
| Applies To | orders for an order payment or refund; other for a fee, adjustment or similar line. |
| Source Integration | The integration that sent it. |
| Created / Updated | When the record was created or last changed. |
| Statement Id, Transaction Id | Pipe17's IDs. Hidden by default. |
How a transaction links to an order
- For an orders line, External Reference ID is the channel's order ID. When it matches an order in Pipe17, it's a link to that order. Plain text means Pipe17 has no matching order.
- An other line, such as a fee, can have an empty External Reference ID. That's expected.
A link confirms the order is in Pipe17, not that the order or its payment is in NetSuite.
Filter transactions
| Filter | Use it to |
|---|---|
| Ext Statement ID | Show the lines of one payout. Matches exactly (Equals) or partly (Contains). |
| Ext Reference ID | Find the lines for an order. Equals or Contains. |
| Ext Transaction ID | Find one line by its channel ID. Equals or Contains. |
| SKU | Find lines for a SKU. Equals or Contains. |
| Status | Show one or more transaction statuses. |
| Created | Limit by when Pipe17 received the line. |
| Exception Categories | Find lines with a type of exception. |
To see every line on one payout, filter Ext Statement ID with Equals, or click View transactions on the statement.
Transaction details
Click an External Transaction ID to open it. The title shows the transaction, a link to its statement, and its status.
- Information (click to expand): Transaction ID, Statement ID, Integration, Created and Updated dates, External Statement API ID and External Reference ID.
- Transaction Fees: each amount in the statement's currency. Show Empty Fees is on by default; turn it off to hide zero-value fees.
- Custom Fields.
- Transaction Activity: Related Events, and Other Transactions on Statement to see the rest of the payout.
- To see the full record, open the ⋮ menu and choose View JSON.
Push statements to NetSuite
Pipe17 pushes statements automatically once the NetSuite flow is on. Push them yourself to resend one, for example after fixing an exception.
To push one or more statements:
- Go to Statements > All Statements and filter the list.
- Select the checkbox on each statement to push.
-
Click Push Statements.
-
In Confirm push of statement, click Yes, push this statement now (or Yes, push all statements now for several). A push can't be undone.
A message tells you how many statements were pushed.
To push every statement that matches a filter:
- Set the filters on All Statements.
- Use the select-all checkbox and choose to select all matching results.
- Check the selected count, then click Push Statements.
- Click Yes, push all statements now.
Pipe17 runs the push as a job. The message links to the job, and you get an email when it finishes.
A successful push means the request was sent. Confirm the Deposit in NetSuite, and check the statement's View Log and Exceptions.
How the NetSuite push works
In the NetSuite ERP V2 integration, turn on Push statement transactions to NetSuite as Deposits (in the newer NetSuite connector, it's called Push statements to NetSuite as Deposits). These settings are under Settings > Statement Transactions:
| Setting | What it does | Default |
|---|---|---|
| Statement status that trigger full transaction sync | Statuses that push the statement and sync all its transactions. | Pending |
| Statement status that allow apply | Statuses that may create or update the Deposit in NetSuite. | Pending, Reported |
| Maximum allowed variance ratio | How far the NetSuite Deposit may differ from the statement total before Pipe17 raises an exception. | 0.1 (10%) |
| Filter statements and transactions by source integration | Push only statements from the selected source integrations. | Empty (all) |
| Filter statements and transactions by extStatementId | Push only the listed external statement IDs. | Empty (all) |
| Split large statements into multiple NetSuite Deposits | NetSuite ERP V2 only. Lets one statement create several Deposits so none exceeds 3,000 payment lines. The newer NetSuite connector doesn't offer it. | Off |
After NetSuite writes the Deposit, the statement moves to Reported. Because Reported also allows apply by default, a later run can still update that Deposit. Fees post to the Deposit's Cash Back lines; a positive variance posts to Other Deposits and a negative one to Cash Back.
With a ratio of 0.1, a statement total of 1,000 allows a difference of up to 100. A bigger gap raises an exception.
For the GL setup, see NetSuite | Settlement Reporting.
Why totals can differ
Statement Total and Deposit Total are both stored on the statement. They differ when the channel's payout figure doesn't equal the sum of its lines, for example when a fee line is missing. Deposit Total is not a live read of the NetSuite Deposit.
The NetSuite Deposit can also differ from the payout when:
- An order on the statement isn't in NetSuite, for example because it was placed before go-live or failed to import.
- Order totals differ between the channel and NetSuite, for example because tax or discounts aren't mapped.
- Fee or adjustment mappings are incomplete.
- Some transactions haven't finished processing.
You see these problems in the Exceptions column on both lists, the Exception Categories filter, and the statement's View Log and Statement Activity.
Troubleshooting
- No statements appear.
Clear the list filters. Check that the statement setting is on in the channel integration, the integration is enabled and connected, and Exclude statements created before this date isn't later than the payouts you expect. - A statement has exceptions or stays Pending.
Open it and check Exceptions, View Log and Statement Activity. In the NetSuite integration, check that the push flow is on and that the statement's status and source integration are allowed. Fix the order or mapping named in the exception, then push the statement again. - A transaction's order isn't linked.
Check Applies To: an other line can have no order. For an orders line, Pipe17 has no order with that external ID, for example because the order was never imported. Check the order in the channel. - The NetSuite Deposit doesn't match the payout.
Compare Statement Total and Deposit Total with the Deposit's Cash Back and Other Deposits lines. Look for a missing order, a different order total, a fee mapping or transactions still Pending. Differences within the variance ratio don't raise an exception. -
Push Statements is missing or the push doesn't reach NetSuite.
Select at least one row. If it's still missing, ask an admin for Statements create or update access (and Jobs create access to push all results). Then check the NetSuite settings above and the job's result.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We're here to help you succeed with your operations.
Comments
0 comments