Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

Import setup

  • Import statement only when all invoices are created in NetSuite

  • Split the statements by defined number of lines per statement

  • Investigate if the lines in statements can be grouped into a batch

Matching setup

  • Make sure there is a unique identifier on the invoice that is also available in the statement file

  • Define matching requirements AND number of transactions to be matched on for that particular matching preference

  • Investigate current matching success by creating the SS of Bank Statement Transaction:

    • criteria: matching reason is none of None

    • results:

      • matching reason - summary type: Group

      • internal ID - summary type: Count

    • sort by: internal ID with “Descending” marked

  • Can you use one of scheduled matching/single value matching?

  • Bank Rec can handle high volume if there is a 1:1 match between invoice and payment based on the unique identifier mentioned above

  • Disable matching on import, enable single-value matching for the high volume bank accounts

  • Limit the matching to 30 days in the past, or less if there are many open transactions in the system

  • Create reminders to know which statements are fully matched and which statements have a few lines left (that likely have to be handled manually)

  • Describe a step-by-step bank rec process for the user to follow

Processing setup

  • Is EFT payments being utilised? How many payments per batch?

  • What type of transactions are being created? What UE scripts are attached on those record types?

  • How many scheduled processed are running in your account, can BR scripts have elevated priority?

  • Consider purchasing SC+ licence?

Formula to estimate processed volume per day

Take the median time in seconds it takes NetSuite to submit the bank transaction that is created mostly (e.g. customer payment). Use the performance monitor for this data.

We assume that 30% of the processor time can be used to create transactions. Another 30% for matching and the remaining 40% for other processes in the system. This assumption can very much differ per customer (depending on the processes that are done in NetSuite) so we cannot be held liable if this is different in your NetSuite account

Take the number of seconds in a day and divide by the number of seconds it takes to submit a transaction. Take 30% of this number. This is the number of transactions that can be created per day per processor. Multiply by the number of Suitecloud processors available in your system. This is the max volume that can be processed in your NetSuite account.

  • No labels