SShortSingh.
Back to feed

Checking Romanian supplier VAT and inactive status via the ANAF API

0
·3 views

Under Romanian tax law, buying from a supplier listed as inactive in ANAF's register blocks the deduction of both the expense and its VAT, subject to certain exceptions. A supplier whose VAT registration was cancelled on specified grounds triggers a narrower rule, costing only the VAT deduction from the day after cancellation. Because a supplier can switch to inactive after a contract is signed, a one-time check at onboarding may not be enough. The article describes ANAF's free keyless endpoint, which checks up to 100 company tax IDs per call, and outlines how to monitor changes while avoiding false alerts from errors or transient 'not found' results. The author notes the content is not tax advice and recommends confirming details with an accountant.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Masttro Launches Read-Only MCP Server for Wealth Data Access by AI Tools

Masttro launched a Model Context Protocol server on November 16, 2026, letting eligible family offices, wealth owners, and advisors connect their wealth records to compatible external AI applications. The server is strictly read-only and exposes holdings, transactions, performance, and entity and ownership structures, while offering no write operations. Access is disabled by default and requires explicit client activation, with administrators able to revoke permissions at any time. Masttro states that once data reaches an external AI provider, its processing and protection fall under that provider's arrangements rather than Masttro's. The article, which is partly promotional for a third-party decision-scoring service, argues that per-read decision controls are not part of Masttro's offering.

0
ProgrammingDEV Community ·

Node.js Reminder Queues: Designing Background Jobs for Safe Retries and Delivery

The article argues that reminder queues in Node.js should be built for at-least-once execution, with idempotent side effects and an explicit terminal state, since a duplicate notification is easier to recover from than a reminder wrongly marked complete. It recommends modeling reminders separately from their attempts, preserving each attempt's history so operators can reconcile outcomes after crashes. Graceful shutdown should stop new claims, let in-flight work finish, renew leases only while progress continues, and reclassify abandoned claims for redelivery. Where a downstream service lacks idempotency keys or receipts, the author suggests an outbox pattern with reconciliation instead of relying on lease-based retries alone. The piece concludes that the queue is only transport, and that the business record must stay explainable after retries and partial failures.

0
ProgrammingDEV Community ·

Two-Hour Talk on How to Think About AI, Recorded by Dmitry Merkulov and Maksim

Dmitry Merkulov of the School of Great Books and a practitioner who builds websites, bots and agents recorded a conversation of nearly two hours on 15 November. They chose to focus less on usage tips and more on how people should approach AI as a way of thinking. The practitioner described how a former hobby became a source of income, while Merkulov brought philosophical and historical context to the discussion. Topics included treating subscriptions as a learning investment, the risk that talk of machine consciousness shifts responsibility away from people, and the "blind archer" approach of running many projects at once. The recording is slated for release on the School of Great Books YouTube channel after editing.

0
ProgrammingDEV Community ·

Benchmark of 11 Linux monitoring agents finds lightest on memory is heaviest on CPU

A developer who builds a monitoring agent tested eleven such tools side by side on identical Hetzner servers, measuring memory, CPU, disk and network use over 24 hours. Idle memory ranged from 9 MB to 358 MB, and the agent using the least memory also used the most CPU at idle. The author's own agent placed fourth of eleven on memory, and the test itself exposed a flaw in that agent, which was fixed before the published run. Each agent was installed with default vendor settings and measured three times, with medians reported. The full data and harness are publicly available so readers can verify the figures.