Marty Zigman

Conversations with Marty Zigman

Certified Administrator • ERP • SuiteCloud

Marty Zigman LinkedIn

Marty Zigman

Holding all three official certifications, Marty is regarded as the top NetSuite expert and leads a team of senior professionals at Prolecto Resources, Inc.. He is a former Deloitte & Touche CPA and has held CTO roles. For over 30 years, Marty has produced leadership in ERP, CRM, and eCommerce business systems. Contact Marty to set up a conversation.

BiographyYouTubeLinkedInX (Twitter)

4 thoughts on “Solving NetSuite Bank Reconciliation Differences

  1. Kane says:

    Great article once again, Marty!

    I didn’t realise I could revert to the legacy reconciliation to fix discrepancies. I knew you could switch, but never thought to try entering a Statement Date of a statement already reconciled using the new Bank Matching method.

    I definitely believe the new Bank Matching/Reconciliation tool needs a lot of work.

    To that end, I actually built my own reconciliation tool that uses undocumented APIs, it works similar to Xero.
    Each transaction is matched and you accept it if you’re happy with it, or you can create a new one on the fly, and even create rules.
    It also supports creating Bill Payments if it finds an outstanding Vendor Bill with no associated Bill Payment.

    We’ve been using in-house for about a year now and it saves us SO MUCH time. I really need to polish a few corners on it and release it as a SuiteApp.

  2. Irra P says:

    Is there a need to reopen the periods when resolving the discrepancies through the legacy feature?

  3. Marty Zigman says:

    Hello Irra,

    No, the beauty is that you can indeed edit a legacy bank reconciliation statement that is in a closed period. Bottom line is that you are effectively marking the cleared/reconciled flag which has no GL impact.

    Marty

  4. Marty Zigman says:

    Hello Kane,

    I welcome the opportunity to learn that SuiteApp if you can provide a reference.

    Marty

Leave a Reply

Your email address will not be published. Required fields are marked *