Transaction processing computer system with multi-channel communication control and decision support

1 . A computer-implemented method of transaction processing with multi-channel communication and decision support comprising:

generating, via a document processing engine, one or more requests for information;

transmitting, by the document processing engine, the one or more requests for information to a requesting party, via a multi-channel communication system;

receiving, via the document processing engine, one or more documents and corresponding metadata transmitted by the requesting party, in response to the one or more requests for information;

automatically processing, via the document processing engine, the one or more documents and corresponding metadata transmitted by the requesting party;

automatically validating, via the document processing engine, the one or more documents and corresponding metadata transmitted by the requesting party;

triggering, via the multi-channel communication system, one or more journeys comprised of first and second tasks, wherein completion of a journey of the one or more journeys results in a communication by the multi-channel communication system;

wherein executing the first task comprises transmitting a first message that is generated by retrieving a first message template from a content management system (“CMS”) and populating the first message template with a message recipient value as found by a back-end component, text from a data store and/or the back-end component, and an information exception embedding that details a difference between a current state of the one or more documents and a required corpus of one or more required documents;

wherein the second task is executed based on a triggering condition that uses information received as a response to the first message, and wherein executing the second task comprises transmitting a second message that is generated by retrieving and populating a second message template from the CMS; and

storing, via a system of record, the one or more processed documents and corresponding metadata.

2 . The computer-implemented method of claim 1 , further comprising automatically matching, via the document processing engine, entities from the one or more documents and corresponding metadata to back-end components.

3 . The computer-implemented method of claim 1 , further comprising automatically categorizing, via the document processing engine, the one or more documents and corresponding metadata according to a canonical document ontology.

4 . The computer-implemented method of claim 1 , further comprising automatically transforming, via the document processing engine, one or more pages of the document one or more documents to enhance legibility.

5 . The computer-implemented method of claim 1 , further comprising automatically identifying, via the document processing engine, conformity and/or nonconformity with exception conditions as defined in a document exception policy.

6 . The computer-implemented method of claim 5 , wherein the document exception policy further includes absence and/or existence of a signature; a signature block matching the name of the requesting party; and a document execution date within a specific time range.

7 . The computer-implemented method of claim 5 , further comprising, in response to nonconformity with exception conditions as defined in the document exception policy, automatically storing the document in a data store for further intervention.

8 . The computer-implemented method of claim 1 wherein each of the one or more journeys further comprise ordered tasks and the ordered tasks are triggered by the completion of one or more prior tasks.

9 . The computer-implemented method of claim 1 , wherein the first message is transmitted such that the first message appears to be sent by a decisioning party.

10 . The computer-implemented method of claim 9 , wherein the information exception embedding further includes:

one or more documents the requesting party expects but has not received;

metadata of the received one or more documents;

information indicating whether or not the one or more documents has been validated;

commentary from the requesting party regarding errors on the document; and

uniform resource locator (“URL”) links to further information on the information exception embedding not directly visible in the embedding but accessible through the URL.

11 . The computer-implemented method of claim 1 , wherein the information exception embedding represents the embedding at a fixed point of time.

12 . The computer-implemented method of claim 1 , wherein the information exception embedding represents the embedding in real-time.

13 . The computer-implemented method of claim 1 , wherein the one or more journeys are each associated with a respective workflow defined in a workflow/customer relationship management system.

14 . The computer-implemented method of claim 1 , wherein populating the second message template comprises populating a second message recipient value as found by the back-end component and populating second text from the data store and/or the back-end component.