How-toSYSPRO 8Localisation / Client / General Ledger integration

SYSPRO 8: What Is E-Invoice, the 8 Client, and GL Integration

Question
syspro 8 what is e-invoice

Also searched as

  • syspro 8 client
  • gl integration syspro 8
  • syspro e-invoicing setup
  • syspro 8 client install

Short answer

An e-invoice is a structured, machine-readable invoice (usually XML) that is validated by a tax authority or exchanged through a network instead of being emailed as a PDF. SYSPRO 8 produces the underlying invoice data; the country-specific e-invoice format and submission usually come from a localisation or partner component, so confirm what your country needs with your SYSPRO partner. GL integration is still configured per module in the setup options, and the SYSPRO 8 client is a managed desktop install that talks to the application server.

Applies to: SYSPRO 8 (all releases) on SQL Server; SYSPRO 7 comparisons where noted. Country e-invoice support varies by release and localisation.

How to work through a SYSPRO 8 e-invoice and GL integration check

  1. 1Identify your legal requirement first: a tax-authority clearance model (India IRN, Mexico CFDI, Italy SDI), a network model (Peppol in the EU, Australia, Singapore) or no mandate. The requirement decides the format, not SYSPRO.
  2. 2Ask your SYSPRO partner which e-invoicing component or localisation your release supports for that country, and whether it needs extra licensing or a separate service.
  3. 3Confirm the invoice data that must exist in SYSPRO: customer tax registration number, ship-to and bill-to addresses, tax codes on every line, units of measure and currency. Missing master data is the usual reason e-invoice validation rejects a document.
  4. 4Check the SYSPRO 8 client deployment: the application server and SQL Server stay in your data centre, and workstations or terminal servers run the SYSPRO 8 client. Keep client and server on the same release and update level.
  5. 5Open each module's setup options (Accounts Receivable, Accounts Payable, Inventory, Purchase Orders, WIP, Sales Orders) and review the General Ledger integration setting and the GL codes it expects.
  6. 6Run a test invoice and a test receipt in a test company, then compare the journals created with the expected GL accounts before touching production.

What an e-invoice actually is

A PDF emailed to a customer is an electronic invoice but not an e-invoice in the regulatory sense. An e-invoice is a structured data document, such as UBL XML, FatturaPA XML or a CFDI, whose fields can be read by software without anyone re-keying them. In clearance countries the seller sends the document to the tax authority first and receives an identifier or digital stamp back before the buyer is allowed to treat it as valid.

That means the work is mostly data quality plus a connector. The ERP must hold clean tax IDs, tax codes and addresses, and something must translate the posted invoice into the mandated schema and submit it. In SYSPRO 8 that translation layer is normally a localisation or integration component rather than a core screen, which is why the right first question is always which country and which authority.

The SYSPRO 8 client

SYSPRO 8 keeps the same split as earlier releases: a SQL Server database, a SYSPRO application server, and clients. The desktop client is installed per workstation or published through a terminal or remote desktop server, and the newer web-based experience (SYSPRO Avanti) and mobile apps connect to the same server side. Pick one deployment model and standardise on it, because mixed client versions cause hard-to-trace runtime errors.

When an upgrade is planned, update the server first, then roll the client in the same maintenance window. Test the client against a copy of production, including any custom forms, reports and e.net integrations. The existing page on SYSPRO 7 to SYSPRO 8 upgrades covers the planning side.

GL integration in SYSPRO 8

SYSPRO modules do not post straight into GL balances. Each sub-ledger and operational module is set up to integrate with the General Ledger either in detail, in summary or not at all, and it builds journals that are then reviewed and posted by the General Ledger module. The setting lives in each module's setup options, and the GL account codes used by a transaction come from the stock code or product class, warehouse, customer or supplier class, and control accounts.

If you are moving from SYSPRO 7, the integration model itself is familiar, so most problems come from the conversion rather than a new design: GL codes not mapped on new product classes, a module left on summary when finance expects detail, or a period not open in the GL. Compare journals from the same transaction in both releases before go-live.

-- Find stock codes whose product class has no GL mapping (adapt names to your release)
-- Run read-only against a copy, and check the real column names with:
SELECT TABLE_NAME, COLUMN_NAME
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME LIKE 'Gen%'
ORDER BY TABLE_NAME, ORDINAL_POSITION;

Try it here, free

SYSPRO Month-End Close Checklist

Open full tool

Tick-off checklist for closing a period in SYSPRO across inventory, purchase orders, WIP, receivables, payables and the general ledger.

Common pitfalls

  • !Assuming the SYSPRO core product will submit to your tax authority. Most countries need a localisation, a service provider or a partner connector.
  • !Mixing client and server release levels after a patch, which produces runtime errors that look like data problems.
  • !Leaving a module on summary GL integration when finance reconciles at transaction level.
  • !Testing e-invoice rules only with clean sample customers; real customers often lack tax IDs or valid addresses.
  • !Posting to a GL period that is closed, so journals sit unposted and the sub-ledger and GL no longer agree.

How an ERP-grounded AI assistant handles this

Netray adds a private AI layer to the SYSPRO you already run, including on-prem installs where the SQL Server and application server never leave your network. ERPray answers questions over live SYSPRO data with read-only SQL or e.net queries it shows you, under the operator's own SYSPRO security, so a planner or accountant can ask the question in plain language and see exactly which tables or business objects produced the answer. Any write-back, such as posting a transaction, goes through a human approval step. The model is open-weight and runs on your own GPUs, so company data is not sent to a public AI service.

See ERPray

Frequently asked questions

Does SYSPRO 8 support e-invoicing out of the box?

SYSPRO 8 holds the data an e-invoice needs, but the mandated format and the submission to a tax authority or network usually depend on your country and a localisation or partner component. Ask your SYSPRO partner what is supported for your release and country, and whether it is licensed separately.

Is the SYSPRO 8 client a web app?

The main client is a desktop application installed on workstations or published from a terminal server, and SYSPRO also offers a web-based interface and mobile apps against the same server. Which you use is a deployment choice, not a different database or product.

How is GL integration set in SYSPRO?

Each module has its own setup option that controls whether it integrates to the General Ledger, and at what level of detail. The GL accounts come from classes and control accounts. Review each module's setup and run test transactions to see the resulting journals.

What changed in GL integration from SYSPRO 7 to 8?

The core model of module journals feeding the General Ledger is the same. The risk in an upgrade is mapping and configuration, not a new design. Compare the same transactions in both releases and read the release notes for your specific version.

Related

CIO briefing

SYSPRO 7 to SYSPRO 8: What an IT Leader Should Plan Before Upgrading

A SYSPRO 7 to 8 upgrade is mostly a customisation, integration and report inventory exercise rather than a data migration problem. List everything that touches SYSPRO, test each item in a copy of production, plan the user interface change for operators, and agree rollback. Check with your SYSPRO partner and current support terms for your version before deciding the timing.

How-to

How to Do a GRN (Goods Received Note) in SYSPRO

In SYSPRO you receive goods against a purchase order in the Purchase Orders module, which creates a goods received note (GRN), puts stock into the warehouse and posts the value to a GRN suspense account. When the supplier invoice arrives, Accounts Payable matches it to the GRN, which clears the suspense and records any price difference.

How-to

SYSPRO Landed Cost Tracking: Freight, Duty and Allocation

Landed cost tracking adds freight, duty, insurance, brokerage and other import charges to the cost of received stock so that inventory carries the true cost to your door. In SYSPRO you define cost types, collect the charges against a shipment or purchase order, allocate them to the received lines by value, quantity, weight or volume, and the stock cost and GL valuation update accordingly.

How-to

SYSPRO Job Will Not Close or Leaves a WIP Balance: What to Check

A SYSPRO job leaves a WIP balance or refuses to close when material, labour or overhead is still sitting on the job without a matching receipt of finished goods. Check that the full quantity has been received through job receipts, that all allocated materials are issued or deallocated, and that outstanding labour is posted. Then close the job so SYSPRO transfers the remaining difference to variance.

How-to

SYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems

SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order.

Error fix

Error validating SYSPRO online profile: what it means and how to fix it

A profile validation error means the SYSPRO client or service could not confirm the operator, company, licence or database connection it was handed at logon. Check the service and licence first, then the operator and company, then the database and disk, in that order. Storage errors are usually full disks, a locked SQL file or a tempdb problem rather than a SYSPRO bug.

AI for ERP

AI for SYSPRO, Grounded in Your Own Manufacturing Data

Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.

AI for ERP

AI for SYSPRO Manufacturing Operations: From Work Centers to Answers

SYSPRO Manufacturing Operations generates data on work centers, routings, and WIP - see how private AI turns it into shop floor answers on-prem.

Stuck on SYSPRO 8?

Talk to engineers who work inside SYSPRO 8 every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software

TermsGeneral Ledger