Block 1 - Code in JavaScript
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow fully automates the reconciliation process between your Local Database transactions and Payment Gateway transactions. It compares both data sources, identifies mismatches...
n8n-nodes-base.code, n8n-nodes-base.comparedatasets, n8n-nodes-base.filter, n8n-nodes-base.googlesheets, n8n-nodes-base.summarize, n8n-nodes-base.merge, n8n-nodes-base.emailsend, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mohamed Abubakkar.
Original n8n.io sourceThis workflow fully automates the reconciliation process between your Local Database transactions and Payment Gateway transactions. It compares both data sources, identifies mismatches, categorizes discrepancies, logs them into Google Sheets, generates a final summary, and sends an automated reconciliation report to your finance team. This ensures accurate, consistent, and error-free financial reporting without manual work.
You must connect the following credentials: Google Sheets (Service Account or OAuth) Email SMTP (Gmail or custom)
Update the workflow with: Your Google Sheet IDs Your tab/sheet names SMTP email, sender, and recipient Optional: Custom domain or business branding
Modify subject, message body, or formatting style based on your reporting standards.
You may choose: Manual Trigger Cron Trigger for daily/weekly reconciliation Webhook Trigger integrated with your system
The workflow reads all transaction records from the Local Database Sheet and Payment Gateway Sheet.
Using the compare operation, the workflow splits result into a. Valid Transactions b. Invalid Transactions c. Amount Differences Transactions d. Missing Transactions
The workflow scans local transactions to detect duplicate transaction and logs them seperately
Each category is appended to its respective Google Sheet:
The workflow counts:
The final summary row is appended to a dedicated Reconciliation Summary Sheet.
The finance team receive a email of final summary report.
At the end the workflow, you get:
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.
| Workflow | Automate payment gateway & database transaction reconciliation with Google Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 26 |
| Categories | Document Extraction |
| Author | Mohamed Abubakkar |
| Published | 11 Dec 2025 |
Use the JSON export at /data/workflows/11684/11684.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow fully automates the reconciliation process between your Local Database transactions and Payment Gateway transactions. It compares both data sources, identifies mismatches...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.