<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zeteo Inc.</title>
    <description>The latest articles on DEV Community by Zeteo Inc. (@zeteoapp).</description>
    <link>https://dev.to/zeteoapp</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4185833%2F86447c74-d165-4d1b-8218-ef08a84fcb5a.png</url>
      <title>DEV Community: Zeteo Inc.</title>
      <link>https://dev.to/zeteoapp</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zeteoapp"/>
    <language>en</language>
    <item>
      <title>How we model a split bank charge so the budget only sees your share</title>
      <dc:creator>Zeteo Inc.</dc:creator>
      <pubDate>Thu, 22 Oct 2026 01:42:58 +0000</pubDate>
      <link>https://dev.to/zeteoapp/how-we-model-a-split-bank-charge-so-the-budget-only-sees-your-share-1l8e</link>
      <guid>https://dev.to/zeteoapp/how-we-model-a-split-bank-charge-so-the-budget-only-sees-your-share-1l8e</guid>
      <description>&lt;p&gt;We shipped Zeteo, a Flutter app for iOS and Android. This post is about one design question, not a pitch.&lt;/p&gt;

&lt;p&gt;The question: a shared dinner is one card transaction of 120 dollars. Your statement says 120. Your budget should say 30. Where does the 30 live?&lt;/p&gt;

&lt;p&gt;Our answer is that the split hangs off the bank transaction. The transaction stays untouched as the source of truth. A group expense references it, and the budget reads your share from the group expense. The rest is an amount other people owe you.&lt;/p&gt;

&lt;p&gt;Data comes in through Plaid, read-only. We never move money. Settle-up hands off to payment apps.&lt;/p&gt;

&lt;p&gt;The trap we hit was timing. Plaid sends a pending transaction first and a posted one on a later sync. A re-sync must not wipe what the user already changed, so we match on the transaction identity and merge instead of replace.&lt;/p&gt;

&lt;p&gt;Questions for people who built on bank data:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do you handle a pending transaction that disappears and returns under a new id?&lt;/li&gt;
&lt;li&gt;Do you key splits on the transaction id or on a fingerprint?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://zeteoapp.com/download?utm_source=devto&amp;amp;utm_medium=community&amp;amp;utm_campaign=launch_2026" rel="noopener noreferrer"&gt;https://zeteoapp.com/download?utm_source=devto&amp;amp;utm_medium=community&amp;amp;utm_campaign=launch_2026&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>fintech</category>
      <category>mobile</category>
      <category>flutter</category>
    </item>
  </channel>
</rss>
