Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
.
Hi @ALLLL ,
Could you please confirm if the issue has been resolved? If not, feel free to reach out if you have any further questions.
Your update would be helpful for other members who may face a similar issue.
Best Regards,
Abdul Rafi
Hi @ALLLL ,
Just wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Best Regards,
Abdul Rafi.
Hi @ALLLL ,
Thankyou for choosing Microsoft Fabric Community.
Thanks for the detailed explanation. This looks more like a reconciliation scenario than a simple lookup, especially since one payment can cover multiple invoices, one invoice can have multiple payments, and the matching is based mainly on amount and date rather than a unique identifier.
A few additional details would help clarify the best approach. Do the bank transactions contain any invoice number or customer reference that could help link them to the ERP data? Is there an acceptable date tolerance between invoice date and payment date? Also, are small amount differences common due to rounding or bank fees? Finally, would it be acceptable to automate the majority of matches and manually review only the unmatched or ambiguous cases?
The reason I ask is that Power Query merges work best when there is a clear matching key. In your case, this behaves more like a many-to-many reconciliation problem, so understanding the business rules and data structure will help determine the most reliable solution.
For more information go through the documentation:
https://learn.microsoft.com/en-us/power-query/power-query-what-is-power-query
Best Regards,
Abdul Rafi
| User | Count |
|---|---|
| 12 | |
| 6 | |
| 6 | |
| 5 | |
| 5 |