Coding An End-To-End Credit Card Spend Pipeline In 1 Weekend

Since the last installment of “Zach does way too much work to fix a vendor’s minor shortcoming” focused heavily on rationale, problem context and the act of processing PDFs, I want to dedicate this piece to taking all the pieces of pt I to create an actionable dashboard.

In popular terms, this edition will “make it [execution] make sense.”

Fun fact: The end product of this dashboard is what drove my wife and I to have a retrospective discussion about spending in 2024, something we’ve never done before because we weren’t equipped with the tools to examine our credit cards as a whole entity.

But before combining everything, it’s necessary to take all the raw totals and the few instances where I’m using a SUM() of transaction data and build the sources for the dash.

Build Your Pipeline To A Data Engineering Career

You’ve reached the limit of the public preview. The full version of this post includes the implementation details: The code, the edge cases, and the "why" behind the architecture.

When you join PipelineToDE, you get:

• The DA → DE Pathway Course: A structured roadmap to bridge the gap between analysis and engineering.
• Weekly Senior Deep Dives: Fresh, tactical insights on Python, Cloud (GCP/AWS), and modern orchestration delivered every week.
• Production-Ready Blueprints: Access to 80+ protected stories and code repos from my time in the trenches as a Senior DE
• The DE Job Board (Coming Soon): Exclusive access to a curated board of high-agency Data Engineering roles.