Your templates change. Your software shouldn’t.
SmartDocGen fills your real Excel template straight from raw ERP output, and routes each document to the right place automatically. When a template changes — even a brand-new field — a key-user points it at the data the same day. No deployment. No developer. No consultant.
We map one of your own templates against your real data in the call.
A new cell in the customer’s Excel template: {{customer_vat}}.
Add a field to your Excel. Upload it. It’s already waiting in the mapping screen. Point it at your data. Done — no release, no developer.
A new field shouldn’t need a new release.
Token engines
(Carbone, Plumsail, Formstack)
Your integrator's developer edits the JSON payload — a deployment.
Query-in-template
(Quadient, Lasernet, Exstream)
A developer writes the binding inside the template — compile, package, export, deploy.
SmartDocGen
The field appears by itself in the mapping screen, unmapped — point it at a path — done.
It’s already built. The backend catches every unknown placeholder and waits for you to point it somewhere.
One pipeline, one binding model.
Raw data in
POST the payload your ERP already emits — 5,000 lines of M3 XML or JSON. No reshaping step before it reaches us.
XML · XPATHThe mapping — held outside the template
The binding lives outside the template as data, not code. A key-user points fields at the data in a VLOOKUP-style builder — filter, pick, look up, no XPath to learn.
BINDING OUTSIDEFills your real template
Your actual .xlsx template, merged — not a rebuilt lookalike. Formatting stays intact.
.XLSX NATIVERoutes automatically
No hint of which template applies in the payload. The platform matches the content and generates the right document(s).
CONTENT-MATCHEDDelivered where it belongs
soonDelivered to your file store today. Word output and SharePoint delivery are next.
.DOCX · SHAREPOINTThree situations you already recognise.
Templated Excel from your ERP’s raw XML
Infor’s own IDM produces Excel only from a flat CSV dump, never from the M3OutDocument XML your system emits — templated Excel from that XML requires a separately-licensed Exstream. SmartDocGen takes the raw XML directly.
Filed straight into your storage
SharePoint soonDelivered to your file store today. SharePoint is next — the enterprise tools file to Documentum, S3, Azure, Kafka, but never SharePoint, since they sell competing ECM.
The rebrand deadline
“New logo, 1 January.” Every template changes, on an agreed date. Schedule the new template version in advance; the first document generated after the moment uses it automatically — no midnight release window.
Common questions.
Do I need a developer to change a document template?+–
No — that’s the whole point. Initial setup can involve IT, but changing a template or adding a field afterwards is done by a business user, because the mapping is data, not code.
Can it fill Excel from my ERP’s XML?+–
Yes. Raw XML in; your real .xlsx out. No reshaping step.
Is there AI in it?+–
No. "Smart" means you no longer need a software deployment to change a template — not machine learning. Generation is deterministic.
How is this different from Plumsail / Carbone?+–
They fill Excel too — from JSON. Someone has to reshape your ERP output into that JSON first, and that’s a developer with a deployment. We take the raw XML and hold the mapping outside the template.
What does it cost?+–
Talk to us — we scope it on a short call.
Bring your template. We’ll map it live.
We map one of your own templates against your real data in the call.