<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/df34820d5c5447f197341a447c7b03b4&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/df34820d5c5447f197341a447c7b03b4-4ca9cdf01cbad59f.gif</thumbnail_url><duration>185.782</duration><title>Civic Ledgers Audit-Ready Transaction Matching Demo</title><description>I created Civic Ledgers, an audit-ready intake and reconciliation layer for local government financial teams. I noticed teams spend a lot of time manually matching invoices and payments during audit season, and current tools store data but do not connect it well. Civic Ledgers pulls information from invoices and files, matches documents to the right transactions, and lets analysts review items as matched, pending, or review. I demonstrated starting with 30 transactions from a sample CSV, running a match, and then confirming or rejecting uncertain matches with AI plain English explanations. No action was explicitly requested from viewers.</description></oembed>