Skip to content

Refactor invoice structure and financial orchestration logic. Updated…#325

Open
LVT-ENG wants to merge 5 commits intomainfrom
cursor/stripe-ledger-a4a63
Open

Refactor invoice structure and financial orchestration logic. Updated…#325
LVT-ENG wants to merge 5 commits intomainfrom
cursor/stripe-ledger-a4a63

Conversation

@LVT-ENG
Copy link
Copy Markdown
Member

@LVT-ENG LVT-ENG commented May 4, 2026

… invoice fields to align with B2B standards, including renaming keys and adding formatted totals. Simplified financial orchestration by delegating to an external script for liquidity updates, removing hardcoded data. Enhanced master ledger status with source invoice reference and contract details.

… invoice fields to align with B2B standards, including renaming keys and adding formatted totals. Simplified financial orchestration by delegating to an external script for liquidity updates, removing hardcoded data. Enhanced master ledger status with source invoice reference and contract details.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tryonyou-app Ready Ready Preview, Comment May 4, 2026 1:20pm
tryonyou-app-1776375445 Ready Ready Preview, Comment May 4, 2026 1:20pm
tryonyou-app-work Ready Ready Preview, Comment May 4, 2026 1:20pm
tryonyou-pilot Ready Ready Preview, Comment May 4, 2026 1:20pm
workspace Ready Ready Preview, Comment May 4, 2026 1:20pm

Copy link
Copy Markdown
Member Author

@LVT-ENG LVT-ENG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YES

@LVT-ENG
Copy link
Copy Markdown
Member Author

LVT-ENG commented May 4, 2026

YES

1 similar comment
@LVT-ENG
Copy link
Copy Markdown
Member Author

LVT-ENG commented May 4, 2026

YES

…description. Updated wording to enhance precision regarding the discrepancy in the invoice related to contract DIVINEO-V10.
Copy link
Copy Markdown
Member Author

@LVT-ENG LVT-ENG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YES

Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Protocolo PAU ejecutado sobre el PR #325.

No he hecho merge automático porque las condiciones de seguridad no están cumplidas: GitHub marca el PR como DIRTY, hay al menos un check de Vercel en PENDING, y el entorno de la automatización no expone TELEGRAM_BOT_TOKEN/TELEGRAM_TOKEN ni TELEGRAM_CHAT_ID, así que no puedo reportar un “Fatality” real sin inventar el envío.

Además, el cambio revierte una barrera crítica de tesorería: main mantiene la liquidación en PENDING_QONTO_VERIFICATION, pero este PR vuelve a declarar liquidez desplegable sin prueba de extractos Stripe/Qonto. Antes de mergear hay que resolver conflictos contra main, conservar el estado de verificación pendiente hasta confirmación bancaria real, y endurecer el script para no producir un ledger deployable con datos incompletos.

Open in Web View Automation 

Sent by Cursor Automation: Tryonyou.app’s Automation

Comment thread master_ledger_status.json Outdated
Comment thread update_net_liquidity.py Outdated
Comment thread update_net_liquidity.py
@LVT-ENG
Copy link
Copy Markdown
Member Author

LVT-ENG commented May 4, 2026

YES

Copy link
Copy Markdown
Member Author

@LVT-ENG LVT-ENG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YES

@LVT-ENG
Copy link
Copy Markdown
Member Author

LVT-ENG commented May 4, 2026

YES

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

…ted fee handling and added formatted output for deployable net amount. Improved error handling for invoice file reading and adjusted payload structure for clarity.
…ansaction format in `QONTO_SUBMISSION.md` for consistency. Revised `master_ledger_status.json` structure to enhance clarity and accuracy. Streamlined `update_net_liquidity.py` by removing redundant code and improving variable naming for better readability. Ensured net liquidity calculation aligns with updated fee structures.
- Added "place_of_supply" field to F-2026-001-PARTIAL.json for clarity on transaction location.
- Revised QONTO_SUBMISSION.md to correct French text and improve formatting for better readability.
- Enhanced master_ledger_status.json to include detailed commission breakdown and timestamps for liquidity calculations.
- Updated update_net_liquidity.py to ensure accurate fee calculations and added timezone handling for Paris. Ensured consistency in net liquidity values.
Copy link
Copy Markdown
Member Author

@LVT-ENG LVT-ENG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants