Customer Invoice & Payment Portal

For most B2B sellers on NetSuite, the slowest part of getting paid is not the customer's willingness to pay. It is the friction around it. A buyer's accounts payable clerk emails asking for a copy of an invoice from four months ago. Someone asks for a statement of account. A customer wants to pay three invoices at once but only has a link for one. Remittance advice arrives as a PDF attachment with no reference, so the payment lands unapplied and your AR ageing lies for a week.

Every one of those interactions costs your AR team time and adds days to DSO, and none of them require human judgement. They are lookups and self-service actions that the customer would happily perform themselves if you gave them somewhere to do it.

This is a branded self-service portal built to order on your NetSuite account. It is not a listed app, and it is not instant. ECOSIRE scopes your invoicing, credit and payment processes, quotes a fixed price, then builds and installs a SuiteScript 2.1 SDF project in your sandbox before it reaches production.

What ECOSIRE builds

A portal your customers can actually reach

The portal is delivered as Suitelets deployed as Available Without Login, or against a Customer Center role where you prefer authenticated NetSuite access — the choice is made during scoping based on your security posture. Public deployments use tokenised, expiring access links tied to a specific Contact and Customer record, with tokens stored hashed on a custom record and rate-limited server side. There is no anonymous browsing of your receivables ledger.

Open items, in real time

The landing page is driven by saved searches over Invoice, Credit Memo, Customer Deposit and Customer Payment records, so the balance the customer sees is the balance in NetSuite at that moment, not a nightly extract. Items are grouped by due date with overdue amounts separated. Each row links to the invoice PDF rendered from your Advanced PDF/HTML Template, so the document the customer downloads is the same document you issued.

Statements and history

Customers can generate an open-item or activity statement for a date range they choose and download it as PDF, using your existing statement template. Closed and paid history is available too, which removes the single most common inbound AR email — the request for a copy of an old invoice.

Paying, including partial and multi-invoice

A customer can select several open invoices, adjust amounts where you allow partial payment, and pay in one transaction. On success the connector creates a Customer Payment record applied across exactly the invoices selected, in the customer's currency, into the Accounting Period and bank or clearing account you nominate. If you would rather review before posting, the portal can instead create the payment in a pending state on a custom record for AR approval. Gateway choice is yours; the payment layer is built against whichever provider you already use, and gateway webhooks are handled by a signature-verified RESTlet with an idempotent event ledger so a retried callback never creates a duplicate payment.

Remittance and short payments

When a customer pays less than the open amount, the portal captures a reason and an optional note against the line. That is written to a custom record linked to the invoice and surfaced in a saved search for your collections team, which turns a mystery short-payment into a queued dispute with context attached.

Contacts, permissions and multi-entity access

Access is granted per Contact record, so a buying organisation can have an AP clerk who can pay and a controller who can only view. Where a customer is a parent with child customers, or trades with several of your subsidiaries in a OneWorld account, the portal can present a consolidated view scoped to exactly the entities that Contact is entitled to see. Entitlement is checked server side on every request, never inferred from the URL.

Branding

The portal carries your logo, colours and typography, is responsive on mobile, and can be served on a subdomain you control. Email notifications — new invoice available, payment received, statement ready, overdue reminder — use your existing email templates and are triggered by User Event and Scheduled scripts.

Operations and audit

Every portal session, document download and payment attempt is logged to a custom record with the acting Contact, timestamp and outcome. Saved searches show active tokens, failed payment attempts, disputed lines and portal adoption per customer. A Scheduled script emails a daily digest to your AR mailbox. Because every posted Customer Payment links back to the portal event that created it, an auditor can trace any receipt to the person who made it.

Who this is for

B2B sellers on NetSuite with a recurring invoice base and an AR team spending its week answering copy-invoice and statement requests; distributors and service firms who want customers to self-serve without buying seats into NetSuite; and finance leaders trying to reduce DSO without adding collections headcount.

How delivery works

1. Scoping call. We review your invoicing and statement templates, credit terms, currencies, subsidiary structure, existing payment provider, partial-payment policy and the access model you are comfortable with. 2. Fixed quote. You receive a written scope naming every screen, script, record and posting to be built, with a fixed price and delivery window. Nothing starts before you approve it. 3. Build. ECOSIRE develops the SuiteScript 2.1 project and the portal front end. Typical lead time is one working week from approval, extending with the number of screens, entitlement rules and payment providers in scope. 4. Sandbox install. The SDF project is deployed to your sandbox. You and a pilot customer contact walk the full journey — link issue, login, invoice view, statement download, multi-invoice payment, short payment with a reason — and we adjust until you sign off. 5. Production install. The same bundle is promoted to production, live gateway credentials are configured, and we roll out to a small set of customers first before you invite the rest. 6. Support window. A defined post-go-live support period for defect fixes and configuration changes is included in the quote.

What this is not

This is not an off-the-shelf portal you can switch on today, and ECOSIRE claims no certification or partnership with NetSuite or any payment provider. It is custom development on your account, delivered as source you own and can modify. You keep your merchant agreement and your obligations around cardholder data — the portal hands payment capture to your provider's hosted page rather than storing card details in NetSuite.