Prepare the first post-go-live payroll and supplier payment runs as separately authorized releases with a shared cutover boundary. Reconcile what the legacy system already paid, submitted or queued, then verify the new system's eligible population, approved destinations and bank or provider readiness. A successful migration does not prove that the first money-moving instruction is safe to release.
Payroll and accounts payable have different data, approvals and service rules. NetSuite may calculate payroll through a specific service or receive accounting results from an external provider. Establish the actual arrangement before using a checklist intended for another product or country.
Map the legacy ERP, payroll provider, NetSuite payment application, integration platform and bank portal. Record which system calculates obligations, creates files, submits instructions and records settlement. One process may cross several of them.
Check scheduled and queued work at the cutoff. A payment file already uploaded to a bank can remain actionable after the source application is paused. Likewise, an external payroll provider may retain an approved batch independently of the NetSuite interface.
Assign one release authority for each population. The payroll owner, accounts-payable approver and bank signatory may have different responsibilities. Do not infer that the implementation lead can authorize payment merely because they coordinate cutover.
Define the final legacy run and first new-system run using period, payment date and population. Preserve their identifiers so a later reviewer can distinguish a legitimate catch-up payment from an accidental duplicate.
For accounts payable, compare the accepted migrated open items with late payments, credits and holds. Identify documents already included in a legacy instruction, even when settlement has not yet appeared on the bank statement.
For payroll, reconcile the approved employee population, period, prior payments and required accumulated information with the payroll specialist. Joiners, leavers and unusual payments need explicit treatment; employment status alone does not determine whether money remains due.
Keep payment eligibility separate from balance existence. An invoice can be correctly migrated but held from payment. A payroll amount can be calculated but awaiting required approval or provider confirmation.
Record exclusions with their reason and owner. Do not delete them from the reconciliation merely to produce a clean payment file. A held obligation remains part of the business position even when it does not belong in the current release.
Identify whether SuitePeople U.S. Payroll is actually in scope. Its setup and test-mode procedures are service-specific and should not be applied as universal instructions for an external or international payroll provider.
For that U.S. service, setup includes entering year-to-date information or the appropriate no-history selection and running a test payroll. Test batches are removed when Payroll Test Mode is turned off, so preserve required acceptance evidence through the approved process before changing modes.
Confirm setup lead times and payment-date rules with the current service guidance and provider. Enabling a payroll feature is not a last-minute substitute for bank verification, employee setup and completed testing.
For an external provider, test its actual file, approval and funding process. Reconcile the accounting interface separately from employee payment. A balanced payroll journal in NetSuite does not prove that the provider accepted or settled the payroll instructions.
Use the bank or provider's approved testing route. Validate the required format, account identifiers, currency, references and controls. A file that can be opened locally is not necessarily acceptable to the receiving service.
Distinguish format acceptance from authorization to pay. A test acknowledgment may confirm structure without validating every beneficiary or the production funding arrangement. Record exactly what the response establishes.
Review payment destinations through the established independent verification process. Do not rely on newly supplied contact details to verify a sensitive bank change. Keep that control separate from technical file generation.
Protect payroll and banking information in test evidence. Use approved sample data where possible and restrict any necessary real details to authorized participants. Ordinary project chat is not an appropriate place for complete bank or employee payment files.
A fictional company has 50 migrated vendor bills selected for review before its first new-system payment run. Five already belong to a legacy bank instruction awaiting settlement, three are on an approved hold and 42 are eligible for the new run. The groups reconcile to 50.
The five pending legacy items are not treated as unpaid merely because the bank statement has not yet shown the outflow. The team obtains the instruction references and checks their current status through the authorized banking process.
If one of those five is rejected, it enters a controlled decision for correction or replacement. It is not automatically added to the new batch without confirming the rejection and ensuring no other instruction remains active.
The first-run evidence therefore includes 42 approved new instructions, five separately tracked legacy items and three retained holds. The numbers are hypothetical and describe population control, not a recommendation to release any real payment.
Have the preparer create the approved batch and the independent reviewer inspect its population, totals, destinations and exceptions. Confirm that the authorized releaser can access the required service through the supported authentication route.
Check timing against actual bank and payroll cutoffs, including relevant timezones and holidays. The ERP go-live date does not determine those service deadlines. A late start may require a business decision rather than an improvised change to payment dates.
Record the exact artifact or batch the reviewer approved. If it is regenerated or edited, assess whether the earlier approval still applies. A familiar filename does not prove that the contents are unchanged.
Keep the release step deliberate. Leaving payroll test mode, submitting a bank file and approving a provider batch have different consequences. They should follow the organization's authorized process and their own required checks.
After an authorized production release, retain the submission reference and receiving-system acknowledgment. Classify accepted, rejected, pending and uncertain instructions using the provider's actual meanings.
Do not equate accepted with settled. Continue the relevant reconciliation until the business can establish the payment result or a specifically owned exception. A timeout requires investigation before resubmission.
For partial failures, identify the affected instructions and use the approved correction route. Recreating the entire batch can duplicate the successful portion. Preserve the original references and any replacement linkage.
Check the resulting NetSuite records and accounting interface. The bank or payroll provider may complete its part while the ERP remains out of date. Financial reconciliation needs the complete chain, not only one green status.
Once the approved transition conditions are met, retire or restrict obsolete schedules and authorizations through the established access process. Confirm that future runs cannot originate unintentionally from both systems.
Retain the eligible population, exclusions, legacy pending items, approvals, submitted artifact, acknowledgments and settlement reconciliation. Protect the evidence according to its sensitivity and the organization's retention requirements.
Use the first-cycle findings to improve the recurring runbook. A one-time migration exception should not become a permanent unexplained step in ordinary payment processing.
A first-run readiness review with CuriousRubik's NetSuite support services can help align migration evidence with the account and provider workflow. Payroll specialists, finance owners and authorized signatories remain responsible for calculation, compliance and payment release decisions.
No. Confirm the actual payroll service, setup, accumulated information, testing, approvals, funding and provider deadlines. These requirements are separate from general ERP launch readiness.
No. It is specific to that service. External and international providers require their own supported testing and release procedures.
Not until its outcome is established and an authorized decision permits replacement. Absence from a bank statement does not prove that a previously submitted instruction will not settle.
Not necessarily. Interpret the provider's status precisely and retain settlement or rejection evidence. Submission, acceptance and settlement are different stages.
Reconcile each instruction, preserve successful outcomes and investigate uncertain ones. Correct or retry only the approved affected population rather than recreate the whole batch blindly.