HomeVendorsGreytrix
GREYTRIX SOLUTIONS FOR SAGE 300

Two additions that fit around how Sage 300 already works.

Document numbers that carry your branch, location or fiscal-year structure, and WhatsApp delivery for transactions you have already posted. Both add capability only where you need it - standard Sage 300 behaviour continues everywhere else.

SAGE 300 DOCUMENT NUMBERING

Make Sage 300 document numbers follow your business rules

Standard Sage 300 numbering works well for straightforward sequences. Businesses running multiple branches, locations, account sets or fiscal-year conventions often need numbers that carry that information. Define the structure once, map it to the relevant transactions, and Sage 300 generates the correct number when the transaction is posted.

1

Structure defined

2

Mapped to transaction

3

Transaction posted

4

Number applied

G/N Numbering Structures window showing a three-segment structure of prefix, fiscal year and number

1 · Numbering structure - prefix, fiscal year and running number.

G/N Numbering Mapping window mapping structure 001 to O/E Order by Account Set

2 · Numbering mapping - driven here by Account Set.

Sage 300 O/E Order Entry confirming posting completed with order number USA-2026-0001

3 · Number generated on posting - USA-2026-0001.

What drives the numbering

Segments available

Prefix (document type) · Running number · Fiscal year · Location · Custom value

Numbering driven by

Account Set · Location · Account Set + Location · Bank Code · Optional Field

Where nothing is mapped

Standard Sage 300 numbering continues to apply, so rules are added only to the transactions that need them.

A unique Document Structure Code is assigned to each structure, so different document types can follow different numbering rules across sales and purchase transactions.
SAGE 300 WHATSAPP INTEGRATION

Bring Sage 300 transactions directly to WhatsApp

Continue posting transactions in Sage 300 as usual, and keep your existing email process in place. Once a supported transaction is posted, users can also send a configurable WhatsApp message and the relevant PDF straight to the customer or vendor.

1

Transaction posted

2

WhatsApp button clicked

3

Template + PDF sent

4

Customer notified

A posted Sage 300 O/E order with a WhatsApp button, and the message with PDF received in WhatsApp

The WhatsApp button appears on the posted Sage 300 transaction. The recipient receives the message and PDF in WhatsApp.

What can be sent

Accounts Receivable

  • A/R invoices
  • Receipts
  • Customer statements

Order Entry

  • Orders
  • Shipments
  • O/E invoices

Purchase Orders

  • Purchase orders
  • P/O receipts

Current standard scope covers selected Sage 300 A/R, O/E and P/O transactions. Additional screens or workflow requirements can be reviewed separately.

Designed for practical, day-to-day communication

Custom messages

Use different wording for invoices, orders, receipts and other transaction types.

PDF attachments

Send the relevant Sage 300 report together with the WhatsApp message.

Transaction assignment

Choose which supported Sage 300 screens should offer WhatsApp.

Bulk A/R statements

Send customer statements to multiple customers from the statement function.

GET IN TOUCH

Ready to see these in your own Sage 300?

Contact your Sage 300 partner, or talk to ERPAdvance Asia, for product information, pricing, a demonstration or a compatibility check.