The DXC Agent for bank reconciliation payment journal generation allows users to automatically create new customer payment journals for relevant bank statement records. Users can also choose to post and match these journals as part of the agent process, or leave the journal unposted for review.
Customer payments could be created by the Agent for the following scenarios:
| Setup | Do not use remittance, only bank statement | Settle from remittance when paid as per bank statement |
|---|---|---|
| Prerequisites | MS Foundry & Agent parameters | Same |
| Enable feature in feature management | • DXC Agent for finance & supply chain management • DXC Agent for bank reconciliation payment journal generation |
Same |
| All agents | • Agent for Customer Payment Journal Generation | • Agent for Customer Payment Journal Generation • Agent for pending remittance creation |
| Customer remittance import | N/A | • SharePoint • Copilot Cowork • DXC connections • Import periodic tasks |
| Bank account - Customer payment journal posting | • Yes - The journal will be created, posted and automatically matched to the original bank statement line • No - The journal will be created, but not posted |
Same |
| Bank account - Customer payment creation | • Do not use remittance | • Settle from remittance and continue • Settle from remittance only |
| Bank transaction types and Transaction code mapping | • Bank transacton type - Action ‘Generate payment’ or ‘Settle customer invoice’ • Transaction code mapping - Map above bank transaction type(s) for bank account’s ‘Bank statement transaction code’ value(s) |
Same |
| Default description | Not mandatory, but recommended | Same |
| Cash and bank management parameters | N/A | Number sequence ‘Pending remittance id’ |
Start by setting up the prerequisite Microsoft Foundry and DXC Agent for finance & supply chain management - user guide
After deployment, find and enable the following features:
Navigate to Organisation administration > Agents for finance & supply chain management > All agent to setup the applicable agent per legal entity.
When opening the form, it checks for any new agents and self populates from details from code
See below table for information on fields.
| Field | Description |
|---|---|
| Agent name | DXCAgentForBankReconciliationCustPaymentJournalGeneration |
| Agent description | Agent for Customer Payment Journal Generation |
| Agent connection details | Select the agent created in prerequisite Agent connection parameters |
| Agent instructions | Automatically populated with default Agent instructions |
| Agent output format | Automatically populated with default output format |
| Enabled | Set to Yes in order to enable the agent |
| Enable telemetry | See below for more details |
The following Agent knowledge sources are automatically created for this agent based on Number sequences assigned for the applicable Accounts receivable parameter fields.
These can be disabled, edited (for example adding more values), etc.
| Name | Description | Type | Example value |
|---|---|---|---|
| AccountNum | Customer account | Text | The AccountNum will appear in the following format: AG### where ### represents numeric digits. |
| Invoice | Invoice | Text | The Invoice will appear in the following format: CIV-######## or FTI-######## where # represents numeric digits. |
| PackingSlipId | Packing slip number | Text | The PackingSlipId will appear in the following format: SPK-######## where ######## represents numeric digits. |
| SalesId | Sales order | Text | The SalesId will appear in the following format: SO###### where ###### represents numeric digits. |
Set Enable telemetry to Yes to log and view telemetry for applicable agents.
View the telemetry by using Go to dashboard on the ActionPane. This is only enabled for applicable agents.
Per each run, the following telemetry could be logged per agent. The data is displayed by month:
Utilised for creating the Customer remittance pending payments from Agent Email Content.
| Field | Description |
|---|---|
| Agent name | DXCAgentForPendingRemittanceCreation |
| Agent description | Agent for pending remittance creation |
| Agent connection details | Select the agent created in prerequisite Agent connection parameters |
| Agent instructions | Automatically populated with default Agent instructions |
| Agent output format | Automatically populated with default output format |
| Enabled | Set to Yes in order to enable the agent |
This agent doesn’t require any Agent knowledge sources.
Create a storage location for customer remittance extracted files in SharePoint.
The required folders are:
Where the ‘Settle from remittance’ process will be used and the pdf customer remittance is received via email, an option to extract the relevant information from the pdf is to use Copilot Cowork. See the following example Customer remittance extraction instructions.
Cowork identifies relevant emails, creates a json file with extracted remittance information and saves the extracted file to the applicable import storage location, for example SharePoint.
Once the extracted file is created, Cowork is instructed to move the processed email to a different folder in Outlook.
Navigate to Organisation administration > Setup > DXC connection > DXC connection import to setup the SharePoint connection details.
User guide
Navigate to Organisation administration > Agents for finance & supply chain management > Agent email messages.
Setup a batch with the required recurrence for each of the following:
Navigate to Cash and bank management > Setup > Bank accounts to setup the following:
Navigate to Cash and bank management > Setup > Bank transaction types and assign the applicable Action to each bank transaction type. Only the Actions that create a new bank transaction applies.
This feature will review the bank statement records where the Action Generate customer payment or Settle customer invoice is mapped.
Example: Bank transaction type value 01 has Action Settle customer invoice assigned.
Navigate to Cash and bank management > Setup > Advanced bank reconciliation setup > Transaction code mapping and ensure all the applicable bank transaction types are mapped for the bank account.
Example: Company bank account has Statement transaction code value 050 mapped to Bank transaction type value 01.
Thus all bank statement records with Bank transaction code value 050 will be reviewed for Create customer payment with agent.
This feature uses Default description when creating the payment journal line.
Navigate to Cash and bank management > Setup > Cash and bank management parameters.
Navigate to Cash and bank management > Enquiries and reports > Customer remittance pending payments.
This form contains Customer remittance records that could refer to one or multiple invoices as per the customer’s remittance. It is used in creating customer payments from the bank reconciliation and settling all the invoices as per this form. This only applies to where the Bank account’s Customer payment creation is set to either Settle from remittance and continue or Settle from remittance only.
The records can be created from:
The following fields are available.
| Name | Description when created with Process emails with agent |
|---|---|
| Pending remittance id | Unique identifier for the remittance record. Created by using the number sequence Pending remittance id in Cash and bank management parameters. |
| Customer account | Customer account is determined by the first invoice in the remittance. |
| Payment reference | Populated from the remittance. |
| Payment date | Populated from the remittance. |
| Remittance status | Record is created with Pending status. Once used in bank reconciliation customer payment creation, the status is changed to Processed. Users can also manually change a record’s status to Cancelled to exclude it from processing. |
| Currency | Populated from the remittance. |
| Amount in transaction currency | Total payment amount from the remittance. |
| Name | Description when created with Process emails with agent |
|---|---|
| Invoice | Populated from the remittance. |
| Currency | Populated from the remittance. |
| Amount in transaction currency | Payment amount per invoice from the remittance. |
Line details are display fields based on the invoice selected in the Pending remittance lines
The DXC Agent for Bank reconciliation in D365 FSCM can be run by:
See setup for prerequisites.
When importing bank statements with Reconcile after import enabled and the prerequisite setup are met the agent will automatically run the licensed agents assigned to the workflow that is either assigned to the Bank account, Cash and bank parameters or the system default.
The agent can be manually run by navigating to Cash and bank management > Bank statement reconciliation > Bank reconciliation and selecting the applicable reconciliation’s Worksheet.
Where the agent is enabled, the Create customer payment with agent button will be enabled in the Unmatched transactions tab.
Where the Bank account’s Customer payment journal posting was set to Yes, the Customer payment journals are posted and automatically matched to the original bank statement record. The following sections only applies to above set to Yes.
Button Journals will be enabled and allow the user to navigate to the posted journal.
Button Cancel payment can be used to create an “opposite”/reversing transaction and move the posted bank document to unmatched.
Note: Ensure Bank transaction type setup against field NSF in Cash and bank management parameters is the same as your Bank transaction type in your Method of payment. If they differ, standard matching doesn’t allow these two bank document records to matched against each other, and throws the following error: “The criteria to reconcile have not been met. You can reconcile either a single canceled check or two transactions. To reconcile two transactions, the document type must be Other, and the documents must have the same bank account, transaction type, payment reference and have opposite amounts.
Button Customer remittance is enabled for customer payments created using Customer remittance pending payments. This opens the Customer remittance pending payments page, for the selected Remittance record that was used in the payment creation.
Field Pending remittance id is also populated on the bank statement record with the applicable remittance id.
The transactions that have been matched by the Agent can easily be viewed in Matched transactions as these are flagged in Matching rule with DXCAgent.
Note: Reconciliation matching rule DXCAgent is automatically created by the product, but only the name is used for flagging the applicable Matched transactions.
To view Agent reasoning, see Matching justification for more information.
The Matching type will be Generate customer payment.
The following agent numbers are available to view on each bank reconciliation and the General tab:
