New England Systems Group

rob@nesystemsgroup.com

ERP & back office · IT & infrastructure · AI integration

First we find out what the business actually needs. Then we build it.

Systems rarely fail because of the software. They fail because nobody walked the process with the people running it before deciding what to build.

We come out of manufacturing back offices — accounting, purchasing, operations, and sales. We know what a bad month-end feels like from the inside, not from a requirements document. That's what we bring to the technical work.

We work with mid-market manufacturers and distributors, and with the solution providers who serve them.

Start a conversation

How we work

Start with the process

We sit with the people doing the work and find the actual break. Usually it isn't where the org chart says it is.

Then build the fix

Not a findings deck and an implementation quote. Working code in your system, scoped small enough to prove itself.

Whatever the stack allows

NetSuite and SuiteScript are home ground, but the real work is making systems that weren't designed for each other talk. Any open API is fair game.

Practice one

Back office & ERP

A few examples from several hundred scripts, integrations, and automations we've put into daily use across manufacturing back offices.

BIL / 01
Automated billing run
Shipments invoiced on a schedule against a cutoff, so month-end revenue lands where it belongs without anyone chasing a queue.
P2P / 01
Three-way match with ACH payment automation
PO, receipt, and bill reconciled automatically, with remittance detail written into the payment file the bank receives.
P2P / 02
Landed cost and tariff validation
Catches mis-costed receipts before they reach inventory value, with a tariff model that survives rate changes.
TRE / 01
International wire payments the bank accepts first time
An ISO 20022 pain.001 payment file rebuilt to a commercial bank's exact spec after the stock template kept failing validation.
WMS / 01
One-touch pick and ship
A multi-screen fulfillment workflow collapsed into a single action for warehouse staff.
MFG / 01
What can actually be built today
A work order dashboard and capacity scheduler that answers the question from real component availability, not a guess.
AR  / 01
Borrowing base and automatic credit holds
AR aging feeding a lender-ready borrowing base, with credit holds applied at the customer record before an order ships.
EDI / 01
Shipping data flowed into customer EDI documents
What's in each carton moves from the shipping system into big-box trading partner documents without anyone re-keying it.
WEB / 01
Online returns customers can file themselves
One RMA form replacing separate return pages across six brand sites, writing straight into the ERP with no re-entry.
FIN / 01
What each product line really earns
Margin that accounts for the operational cost of carrying a long tail of low-volume items, not just standard cost.

Client detail stays confidential. Happy to walk through the approach behind any of these on a call.

Three problems, start to finish

Same pattern every time: walk the process, find where it actually breaks, build the smallest thing that fixes it.

Invoices going out days after the truck left

Billing · Revenue timing

What was happening
Shipments piled up in a pending queue waiting for someone to work through them by hand. Revenue slipped across month-end depending on who was in the office and how busy the week had been.
What we built
A scheduled billing run tied to a shipping cutoff, invoicing everything eligible without anyone touching the queue, plus an exception list for the handful of orders that genuinely need a human.
Result
Month-end revenue lands in the right period, and the queue stopped being a person's job.

Paying bills nobody had checked against the receipt

Accounts payable · Controls

What was happening
Vendor bills were approved on trust and volume. Price and quantity differences against the PO and the receipt surfaced weeks later, if at all, and payment runs were assembled by hand each week.
What we built
Automated three-way match that holds anything outside tolerance for review, feeding an ACH payment run that writes full remittance detail into the file the bank receives.
Result
Discrepancies get caught before money moves, and vendors stop calling to ask what a payment covers.

International wires rejected by the bank, week after week

Treasury · Integration

What was happening
The standard payment file kept failing the bank's validation. Every international wire was being re-entered by hand in the bank portal, with the error rate that implies.
What we built
An ISO 20022 pain.001 export rebuilt against the bank's own specification, tested field by field until it cleared without manual intervention.
Result
Wires go out straight from the ERP, first time, with no re-keying.

Practice two

IT & infrastructure

Twenty years running the whole stack for manufacturers — network, servers, identity, phones, and endpoints. The ERP work above only holds up if what sits underneath it is sound, and most of the time nobody is looking after both.

NET / 01
Network design, refresh, and multi-site connectivity
Cisco and HP switching, Meraki cloud-managed firewalls and wireless, VLAN and VPN design across locations.
SEC / 01
Identity and access hardening
Microsoft 365 and Entra ID, conditional access policy, MFA rollout, blocking legacy authentication, protected break-glass accounts.
SEC / 02
Email compromise response and recovery
Containing an account breach, restoring the mailbox, and closing the door that let it happen in the first place.
SRV / 01
Server virtualization and hardware retirement
Physical-to-virtual migrations onto VMware ESXi, consolidating aging boxes before they fail on their own schedule.
VOI / 01
Phone systems and voice migration
Mitel and Nortel PBX administration, and moving off aging on-premise systems to hosted voice including Comcast Business VoiceEdge.
PRC / 01
Device quoting, standardization, and lifecycle
Specifying and sourcing endpoints at sensible cost, standardizing the fleet, and planning refreshes instead of reacting to them.
M365 / 01
Tenant, storage, and license cleanup
SharePoint storage reclamation, deduplication, archive strategy, and paying for the licensing you actually use.
WEB / 02
Web platforms and hosting
Drupal, WordPress, and LAMP builds, version upgrades, and commerce sites wired back into the ERP.

Most of our clients don't want two vendors pointing at each other. One group that understands the ERP and the network behind it removes that argument entirely.

Practice three

AI integration

Narrow and practical. AI is very good at reading unstructured documents and turning them into structured records, which is most of what a back office does by hand. We build for that, not for chatbots.

AI  / 01
Document intake and classification
Inbound paperwork read on arrival, sorted by type, and matched to the right order or receipt without someone opening each file.
AI  / 02
Unstructured paperwork into clean records
Packing slips, vendor statements, and remittance advice turned into data your system can act on, with a human reviewing only the exceptions.
AI  / 03
Targeted assistants for one workflow
A tool that does a specific job a specific team does daily, scoped tightly enough to actually be trusted.

We'll also tell you when AI is the wrong tool. Plenty of problems that get pitched as AI projects are a rules change and an afternoon of scripting.

How engagements work

Get in touch

If there's a process everyone works around instead of through, that's where we start.

Tell us what's broken. If we're not the right fit, we'll say so and point you somewhere better.

rob@nesystemsgroup.com