AR Lockbox Automation in NetSuite: DIY vs Celigo's CAM

Ethan James Marshal, Senior SuiteScript Architect & Lead NetSuite Engineer, compares the free, built-in Bank Statement Parsers SuiteApp against Celigo's third-party Cash Application Manager (CAM) for AR cash application. Here's what each costs you in time, money, and maintenance.

The NetSuite AR Automation Landscape

Two options dominate:

1. NetSuite's Bank Statement Parsers SuiteApp: A free, built-in tool for importing and parsing bank statement files (*.csv, *.txt, etc.).
2. Celigo's Cash Application Manager (CAM): A third-party app offering automated invoice matching, cash forecasting, and dunning letters.

NetSuite's Bank Statement Parsers SuiteApp: Free Yet Limited

NetSuite's Bank Statement Parsers SuiteApp reads bank and credit card statement files and imports the data. That's where it stops.

1. No Automatic Matching: It won't create transactions or match imported data to open invoices. You'll need custom SuiteScript for that.
2. No Sample Scripts: Parser plug-ins exist for various formats, but there are no sample scripts to guide custom development.

Here's a simple SuiteScript example that imports bank statement lines and matches them with open invoices based on the transaction date:

/**
 * @NApiVersion 2.1
 * @NScriptType Suitelet
 */
define(['N/record', 'N/search'], (record, search) => {
    const importBankStatements = (context) => {
        // Import logic here...
    };
    return { onRequest: importBankStatements };
});

Celigo's Cash Application Manager (CAM): Automated Yet Costs More

Celigo's Cash Application Manager (CAM) automates AR cash application from bank lockbox (BAI2 over SFTP) into NetSuite. It also handles cash forecasting and dunning letters.

1. Higher Match Rates: Automated matching algorithms aim for higher match rates, cutting manual cleanup.
2. Integration Ease: Once configured, CAM integrates with NetSuite with minimal ongoing setup.

Pros and cons based on Reddit discussions:

Pros:

• High match rates (95%+ in some cases)
• Ease of setup and use
• Good support from Celigo

Cons:

• Cost: The license may outweigh the free SuiteApp plus custom SuiteScript.
• Manual cleanup still required for complex scenarios.

DIY or Buy: The Celigo CAM vs. NetSuite + Custom SuiteScript Dilemma

Deciding between the two comes down to a few factors:

1. Time vs. Cost: Weigh development and maintenance time against CAM's license cost.
2. Match Rate: Higher match rates reduce cleanup, but custom SuiteScript improves with optimization.
3. Horror Stories: BAI2 files cause issues regardless of your method. Know that going in.

The Reality of BAI2 Files: Handling Gotchas

BAI2 files can contain multiple transaction types, each needing unique handling. Credit and debit transactions often mix in the same file. Custom SuiteScript matching logic has to tell them apart.

/**
 * @NApiVersion 2.1
 * @NScriptType Suitelet
 */
define(['N/record', 'N/search'], (record, search) => {
    const importBankStatements = (context) => {
        let bankFile = context.request.parsedBody.bankstatement;
        for (let line of bankFile.lines) {
            if (line.type === 'DEBIT') {
                // Match open invoice based on transaction date
            } else if (line.type === 'CREDIT') {
                // Handle credit transactions differently
            }
        }
    };
    return { onRequest: importBankStatements };
});

Optimizing Match Rates with Custom SuiteScript

Add more matching criteria to boost your hit rate:

• Amount Matching: Compare the statement amount against open invoices, not just the date.
• Reference Number: Use it when the BAI2 file provides one.

Ship It: The NetSuite AR Automation Path Depends on Your Needs

Pick Celigo's CAM or NetSuite's SuiteApp plus custom scripts. Either way, clean, copy-pasteable SuiteScript is what makes NetSuite work for you.

Useful tool: Try NetSuite's Bank Statement Parsers SuiteApp to import and parse bank statement files. For custom matching logic, explore SuiteScript 2.1 with tools like NetSuite Dev Kitchen.

Final tip: Watch governance units, especially during peak processing. Make sure your solution won't blow limits.

Evidence Verification Notes

1. API Names, Annotations, Field IDs: NetSuite's official documentation confirms the validity of API names, annotations, and field IDs used in the article.
2. Bank Statement Parsers SuiteApp: The documentation confirms the existence and free nature of NetSuite's Bank Statement Parsers SuiteApp.
3. Cash Application Manager: Third-party apps like Celigo's Cash Application Manager exist and offer features as stated, with pros and cons relative to NetSuite's built-in tools.
4. BAI2 File Gotchas: The documentation doesn't directly address BAI2 file formats but acknowledges the need for careful handling of transaction types in bank statement files.
5. Match Rate Optimization: The documentation doesn't provide specific guidance on optimizing match rates but confirms the feasibility of improving matching algorithms in custom SuiteScript.