Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Extract provider, description and price automatically; light invoice ledger view

Aberta
  • Algo errado?
#237 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
10/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
typescript
Domínio
backend-api-design, frontend

Direção de pesquisa

The issue says the work shipped the same day, so first check whether any follow-up remains. Read backend/src/invoices/extract.ts and backend/src/routes/emailDocuments.ts for extraction and intake behavior, then inspect the portal invoice ledger described in the issue. Done means the requested provider, description, and price extraction and dense ledger view are in place without overwriting operator-corrected drafts.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

backend enhancement frontend

Request (user intake, 2026-10-04)

Review all invoices and the intake process. Two complaints:

  1. Provider extraction is poor — rows show "Unidentified provider" or raw
    identifiers like "VAT/GST Number DE…". The operator wants name, title and
    price extracted from a forwarded invoice automatically.
  2. The invoice review table is too heavy. Wanted: a dense ledger view like the
    published expense sheet (Date sent, Date paid, Provider, What, Price $,
    Price EUR, Statement, Count) — not the current 4-column review queue.

../dapier may be updated if processing needs it.

Findings

  • The dapier intake contract already carries the email subject and from,
    and backend/src/routes/emailDocuments.ts already auto-processes invoice
    intakes on arrival — the gap is that extractInvoiceText ignored those
    signals and only parsed two PDF layouts (AWS, Stripe), with an issuer
    heuristic that happily returned "VAT/GST Number …" lines.
  • No dapier change is required; normalization lives dataops-side.

Shipped (same day)

  • Extraction (backend/src/invoices/extract.ts): email subject/sender hints
    with a canonical provider catalog; "receipt/invoice from X" anchor; issuer
    plausibility + credibility filters (field-label lines and payment-processor
    noise rejected); generic labeled total/date/currency/invoice-number parsing
    incl. European comma decimals; subject-derived description. Governance kept:
    extraction never invents amountEur/paymentEvidence.
  • Untouched pending drafts are re-extracted automatically when a duplicate
    arrives; new POST /invoices/{id}/reextract action (portal + CLI) upgrades
    old bad rows on demand. Operator-corrected drafts are never overwritten.
  • Portal: the heavy table is replaced by a dense invoice ledger (sheet columns,
    pending first, negative prices, row-click review, compact reprocess form,
    re-extract button on eligible drafts); 44px mobile row floor kept.

Refs #232

Linguagem predominante
TypeScript
Estrelas
2
Forks
0
Nenhum PR com merge em 30d

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DataTalksClub/dataops

Todas as issues de DataTalksClub/dataops

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.