Style Netto the same size/weight as the MwSt annotation
Validate e-invoices / mustang (push) Successful in 21s

Was using summaryLabel/summaryValue (fontSize 10, same as Zwischensumme/
Versand — the build-up rows above Gesamt), which visually competed
with Gesamt instead of reading as supplementary detail below it. Now
uses the same small/muted vatNoteLabel/vatNoteValue as the "enthält
X% MwSt." line right above it — both are detail underneath the hero
Gesamt figure, same visual tier.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Marco
2026-07-23 21:33:57 +00:00
parent 3922ea12e1
commit c28ceb7bd3
2 changed files with 15 additions and 6 deletions
+8 -3
View File
@@ -416,10 +416,15 @@ export function InvoiceDocument({ order, seller }: { order: InvoiceOrder; seller
consistency across every invoice this shop issues. Placed
last (after the MwSt annotation, not before it) — see
that annotation's own comment above for why the order
matters here. */}
matters here. Styled with the same small/muted
vatNoteLabel/vatNoteValue as that annotation, not the
larger summaryLabel/summaryValue the build-up rows above
Gesamt use — Netto is supplementary detail *below* the
hero Gesamt figure, same visual tier as the tax
breakdown, not another primary line competing with it. */}
<View style={styles.nettoRow}>
<Text style={styles.summaryLabel}>Netto</Text>
<Text style={styles.summaryValue}>{formatPrice(rateGroups.reduce((sum, g) => sum + g.net, 0))}</Text>
<Text style={styles.vatNoteLabel}>Netto</Text>
<Text style={styles.vatNoteValue}>{formatPrice(rateGroups.reduce((sum, g) => sum + g.net, 0))}</Text>
</View>
</View>
{paid && (