Report and Print Layout Customization Pack

The problem with out-of-the-box document output

SAP Business One ships with generic system print layouts. They carry no brand identity, they hard-code a single language, and they rarely satisfy the exact wording, tax breakdowns, and legal footers your jurisdiction and your customers expect. So finance teams work around it: exporting to Excel and rebuilding invoices by hand, keeping a parallel Word template for delivery notes, printing statements one document at a time, then attaching each PDF to a manually composed email.

The cost shows up in three places. Documents go out inconsistent, so the same customer receives an A/R Invoice and a Delivery note that look like they came from two different companies. Multi-language customers get output they cannot read, or they get a hand-edited copy that no longer matches the posted document. And month-end statement runs consume hours of clicking because nothing batches.

ECOSIRE builds a layout and output pack that closes all three gaps inside SAP Business One, so the printed and emailed document is generated directly from the posted marketing document — never re-keyed.

What ECOSIRE builds

Crystal Reports layouts bound to real SAP B1 documents

We author Crystal Reports layouts against the SAP Business One tables and register them in the Report and Layout Manager so they become the default layout for the document type. Each layout is built for the specific object you need: A/R Invoice (OINV/INV1), A/R Credit Memo, Delivery, Sales Order, Sales Quotation, Purchase Order, A/P Invoice, Incoming Payment receipt, Journal Entry voucher, Inventory Transfer, Pick List, and Business Partner statement of account. Layouts read document header, line, tax, and withholding structures directly, plus any UDFs you already maintain, so nothing is duplicated or recalculated outside the database.

Multi-language document rendering

We drive language selection from the Business Partner master, not from whichever operator hits Print. The layout resolves labels from a Language Text user-defined table (UDT) keyed by document type, field, and language code, so a single registered layout renders in every language you configure. Item descriptions can be sourced from the Business Partner catalogue numbers or from a per-language item description UDT, depending on what you already populate. Right-to-left scripts are handled at the layout level with mirrored sections and appropriate embedded fonts.

Tax and statutory presentation

Tax content comes from the document's own tax lines and tax code definitions, so what prints matches what posted. We build the breakdown your regulator expects: per-rate subtotals, exempt and zero-rated separation, tax amount in local currency alongside document currency where a reporting-currency rate applies, withholding tax lines, rounding disclosure, and the fixed legal text and registration identifiers your jurisdiction mandates. Where a compliance regime requires a machine-readable mark on the printed document, we render it from data your company database already holds.

Batch printing

We build a batch output screen as a User-Defined Object (UDO) with its own selection criteria — document type, date range, series, Business Partner group, sales employee, or a custom UDF flag. The batch job resolves the correct layout and language per document, renders each one, and writes a combined or per-document PDF to a configured path. A log UDT records every render with document key, layout used, language, timestamp, output path, and result, so a failed run is diagnosable rather than mysterious.

Email dispatch

The same engine attaches the rendered PDF and sends it using the Business Partner's contact email, with subject and body templates that resolve document fields and honour the Business Partner's language. Dispatch runs through the Service Layer for document reads and writes back a send record against the document — status, recipient, timestamp, and attachment name — so support staff can answer "was this sent?" from inside SAP Business One. Optional approval gating means nothing leaves until a named user releases the batch.

Configuration instead of code changes

Mapping tables live in UDTs with a maintenance screen: which layout serves which document type and series, which language falls back to which, which email template applies to which document type, and which output folder receives which batch. Adding a series or a language later is a configuration entry, not a rebuild.

Who this is for

Companies running SAP Business One that send documents to customers in more than one language, that operate under a tax regime with prescriptive invoice content, that send monthly statement or invoice runs large enough that one-at-a-time printing is a real cost, or that simply need their documents to look like their brand. It suits distribution, manufacturing, professional services, and any multi-entity group that needs consistent output across several company databases with different letterheads.

Compatibility

Built for SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or hosted. Delivered as an add-on plus registered Crystal Reports layouts, using the Service Layer (REST) and the DI API for document access and write-back, with UDFs, UDTs, and UDOs for configuration and logging. No modification of SAP system tables.

How delivery works

1. Scoping call. We review your current layouts, the exact document types in scope, your languages, your statutory content requirements, your series and numbering, and how you want batches and email triggered. You send sample documents — including ones you have been producing outside SAP Business One — and we work to those as the target.

2. Fixed quote. You receive a written scope listing every layout, every language, the batch and email behaviour, and the acceptance criteria, with a fixed price and a delivery date. Nothing starts until you approve it.

3. Build. We develop against a copy of your company database so layouts are exercised with your real item descriptions, tax codes, UDFs, and Business Partner data rather than demo data.

4. Install in test. We install into your test company, register the layouts, load the configuration tables, and run a documented acceptance pass: each document type printed, each language rendered, a batch run executed, and an email dispatched to an internal address. You sign off against the acceptance criteria from step 2.

5. Install in production. After sign-off we install into your production company during an agreed window, retaining your existing layouts so you can revert to them.

6. Support. A defect-fix window follows go-live, covering anything that does not behave as the accepted scope describes. Layout changes beyond that scope are quoted separately.

Build-to-order, stated plainly

This is not a pre-built product you download and install. There is no trial version and no instant download, because the layouts are authored against your data, your statutory wording, and your brand. Typical lead time is one working week from quote approval, driven mostly by how many document types and languages are in scope and how quickly test-company access and sample documents arrive.