Liaison Software Corporation
11 Orchard, Suite 108
Lake Forest, CA 92630
800.811.4618  - 714.543.9877  -  Fax:  714.543.0887

Get Directions

© 2019 Liaison Software Corporation.

ABOUT US

Liaison Software Corporation is a privately held company, located in Southern California. Founded in 1993, Liaison Software developed the first commercially available DOS-Windows cross-platform CRM system. That product, Liaison CRM, is still available today in it's 6th version.

Liaison Software Company, LLC incorporated in March of 2001 and was renamed; Liaison Software Corporation. 

During the 2000s, Liaison focused their efforts into expanding their Liaison Messenger product into the booming Microsoft Great Plains and Solomon IV Accounting market which later became Microsft Dynamics GP and SL. Liaison Software Corporation is a Certified Partner and Certified Independent Software developer for Microsoft Corporation as well as a strategic Development Partner for Sage Software.

Becoming an Integrated Solutions Vendor for Epicor in 1995, Liaison has expanded its offerings and now develops Workflow Automation Solutions that supports a wide array of accounting systems with an emphasize for Sage Software’s Sage 100, Sage 300, Sage 500, & Sage X3 and the entire line of Microsoft Dynamics AX, GP, SL, NAV, and 365 products.

Liaison Messenger EDD

Case Studies

Invoices:    The process begins with the end-user Printing Invoices out of their accounting system just like they've always done. The only difference  would be 

selecting the Liaison Messenger EDD printer driver.  The print stream is then routed to the Messenger EDD Server and executes the respective script for that document type.  The Messenger EDD server, scripts, etc are executed on the server. It is 100% transparent to the end-user printing the documents. As you can see, the only training is selecting our printer driver, which, can also be assigned to the documents (Invoice) as the default printer.

Attach Outstanding Invoices to Statement in One PDF with Variable Attachment Feature

CHALLENGE:     Would like to send AR Statements including copies of every outstanding invoice that appears on the statement.

 

SOLUTION:      This actually is quite simple and not described around any one customer in particular. In fact, we would bet 90% of our user base does it this way.  When the Liaison Messenger EDD Server installation wizard is performed, the scripts that run the Invoices, as well as the AR Statements, are pre-configured to perform this task automatically by default.
 

On the Messenger EDD Server, the invoice print stream is received and the Invoice script (that appears below) executes automatically with no user intervention.

Line 1:

Sends a copy of the Invoice to the Customer using their preference (email, fax, ftp, or printed and mailed)
Line 2:

Creates a copy of the Invoice and stores it in the designated folder which they will use for Archiving (or document management)
Line 3:

Sends a copy of the Invoice to the Salesperson (of that account) using the salesperson's preference (email, fax, or printed to their printer)

Upon first-time installation, the end-user runs an Archive Only process that recreates all of the historical invoicesand establishes the designated archive folder with a copy of every invoice.

AR Statements:
Just like printing Invoices, the end-user simply prints Statements out of their accounting system and directs the output to the Liaison Messenger EDD printer driver where the print stream is sent to the Messenger EDD Server.  

On the Messenger EDD Server, the AR Statement script looks like this.

Line 1: Sends a copy of the Statement to the Salesperson (of that account) using their preference (EXCLUDING the outstanding Invoices)
Line 2: Creates a copy of the Statement and stores it in the designated Statements folder (EXCLUDING the outstanding Invoices).
Line 3: Intelligently "reads" the Statement and pulls a copy, from the designated Archived Invoice folder, of each Invoice and Assembles the Document 
Line 4: Sends a copy of the assembled Statement to the Customer using their preference (email, fax, or printed and mailed)

All this was accomplished simply by printing to our printer driver. The complexity and distribution takes place on the Messenger EDD server without any user intervention...