This guide provides the necessary steps to re-import missing deposit records into NetSuite by leveraging system configuration settings. This process is crucial for ensuring accurate financial reporting and reconciliation for Braintree and PayPal payouts.
The Core Strategy
Our approach utilizes the system's "Lag to bring payout related records" setting to look back a specified number of days, effectively backdating the payout import flow to capture the missing deposits.
Step 1: Configure the Payout Lag
The first and most critical step is calculating and setting the "Lag to bring payout related records" value to match the date range of your missing deposits.
-
Identify the Range: Determine the Current Date (today) and your Desired Backdate (the specific date you need to start importing from).
-
Calculate the Lag Value:
-
Calculate the total number of days between the Current Date and the Desired Backdate.
-
Subtract 1 day from this total difference.
-
Enter this resulting number into the Lag to bring payout related records field.
-
See below for two sample scenarios.
-
| Goal | Current Date | Lag Offset Set in System | Custom Run Date to Use |
|---|---|---|---|
| Import 1 day of data (e.g., May 31) | June 15, 2025 | 14 days | June 14, 2025 (1 day prior) |
| Import 2 days of data (e.g., May 31 & June 1) | June 15, 2025 | 13 days | June 13, 2025 (2 days prior) |
Step 2: Add a Temporary Dummy Mapping (Recommended Best Practice)
Before running the backdate flow, we recommend temporarily implementing a dummy mapping. This prevents the newly retrieved deposits from immediately importing and posting to NetSuite, giving you a chance to validate the data first.
-
Action: In the deposit import configuration, add a mapping that redirects a critical field (like the deposit date) to a non-critical or different field.
-
Purpose: This effectively blocks the deposit import while allowing the system to fetch the missing records.
-
Example:
**
Step 3: Run the Flow with a Custom Date**
Once the Lag is configured and the dummy mapping is in place, you can execute the flow.
-
Custom Date Setting: Run the payout import flow using a custom date set to one day prior to the current date.
- Example: If today is June 15, 2025, run the flow with June 14, 2025.
-
How it Works: The combination of the custom run date and the large lag offset instructs the flow to pull in all payout data that falls within the calculated backdated window, starting from your target date.
**
Step 4: Review and Finalize the Import**
After the flow has executed and retrieved the missing data (now in a state ready to retry), perform the final steps.
-
Review: Verify the data output from the backdate import process.
-
Remove Dummy Mapping: Once the data is validated, remove the dummy mapping to enable the deposits to correctly post to NetSuite.
-
Retry: Retry the flow to process the records that were previously missing or errored, completing the backdated import into NetSuite.